ContributionsMost RecentMost LikesSolutionsSame API Call on different PCs showing different raw data Co Worker's Raw Header... POST http://<Redacted>:5400/prepack/v1/Send HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json USER-MASTER-EX2: 3bYayeLNgbePbZBF/+vAjxgKLE/R7a7e327qYBL1IsW2mcTxMxtMY6DDFFPX/b/qSfJqbFvPYeWhg9/GSOeKJVW5NzZ6yLLHoJ13r4izrGfKR8iJT2q3tO6dLsru69eBu82N2m06p7Rfa1clnICh4wCX1+AWhGZO9cAQAAyKlyiCJ4hgo2p4G5h3Gq1uFBT82JWN0sUtB7orYHRt0= Content-Length: 42 Host: tra<Redacted>.com:5400 Connection: Keep-Alive User-Agent: Apache-HttpClient/4.1.1 (java 1.5) Mine POST http://<Redacted>:5400/prepack/v1/Send HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: application/json USER-MASTER-EX2: 3bYayeLNgbePbZBF/+vAjxgKLE/R7a7e327qYBL1IsW2mcTxMxtMY6DDFFPX/b/qSfJqbFvPYeWhg9/GSOeKJVW5NzZ6yLLHoJ13r4izrGfKR8iJT2q3tO6dLsru69eBu82N2m06p7Rfa1clnICh4wCX1+AWhGZO9cAQAAyKlyiCJ4hgo2p4G5h3Gq1uFBT82JWN0sUtB7orYHRt0= Content-Length: 42 Host: tra<Redacted>.com:5400 Connection: Keep-Alive User-Agent: Apache-HttpClient/4.1.1 (java 1.5) {"OrderNumber": 23126429, "LineNumber": 1} <== THIS IS DIFFERENT! Both of us have the following: When we execute the above, both of us have exactly the same result... It is just that my raw view of what is getting sent seems to be more "complete".... what setting are we overlooking?: SmartBears Definition of Cross Browser Testing is ? When I think of cross browser testing, I envision a set of tests that produces a report highlighting any differences noted, complete with onion skins to highlight display issues, and indications of flow divergence... The "Ad copy" on the Smartbear site says that Test Complete Does this... so my manager asked me to begin... ummmm Am I missing something? I can't figure out where to begin... Or, was that all "jargon" meant to imply that a script can run on more then 1 browser... Re: Looks Like TC11 does NOT support Chrome 45.0.2454 or later! Yup. and yours is the accepted solution over there. The only tiny wrinkle was that you need to check that you are a Developeror you will not be allowed to check "Enabled" (And, spelling out, for the benefit of SmartBear Documentation Engineers, the issue of Chrome's new policy re: Extensions) Re: Looks Like TC11 does NOT support Chrome 45.0.2454 or later! There was a step I was missing (Because it was not really spelled out, in depth....) After a completly new installationisdone, if you do nothing else, you will NOT be able to use Chrome. If you had chrome & a previous version, after the upgrade, you SHOULD be able to use Chrome What is amiss? Chrome just changed a bunch of stuff, in the interest of security. One of the changes requires the following modifications to Chrome: Go to chrome://extensions/ on the very top, check "Developer Mode" Browse down to the TestComplete addin. It will NOT be checked..... Check it, restart Chrome, Life is good. With that set of steps, I am now cooking with gas :) Looks Like TC11 does NOT support Chrome 45.0.2454 or later! For details, read this thread: http://community.smartbear.com/t5/Functional-Web-Testing/Custom-Web-Objects-are-opaque-to-TC-TC11-Angular/m-p/105788#U105788 I thought I waschasing an angular issue. Turns out, TC 11 CAN NOT PROCESS CHROME 45.0.2454+ WEB PAGES! All you get is NOT GOOD! SolvedRe: Custom Web Objects are opaque to TC? (TC11 + Angular) Well of COURSE it works in other cases... I mean Why would Smartbear release a broken patch? Here, let me open the Smartbear site and....ummmmmmm Wait... How about Google.com ? Oh good lord. You are correct! This is The SmartBear site: And, to confirm your suspicians, here is google itself: So... let's take a quick looksee... Chrome Version:45.0.2454.93 Updated while I looked... sigh. Now it is: Chrome Version 45.0.2454.99 Test Complete Version: 11.10.1005.7 So, How do I know if the version of Chrome I have is supported? (The Chrome Patch page only goes to 43, but it is all for TC10... nothing for TC11 or 11.1) Well, there is this: So........... Is it my imagination, or do we have to come out and say... Yo, SMARTBEAR....TC no longer supports Chrome! Re: Custom Web Objects are opaque to TC? (TC11 + Angular) One would think that, huh... But, as I said in the first line... TC 11.1, all patched and happy... Actually, that's a wee bit off. I am running Chrome 45. THis version, and all to come after, are no longer playing well with the old Plug-in methods. TC 11.1 has rolled the plugin INTO the main program... For people who run on an older TC, if you can not upgrade to a newer version, I would recommend getting a specific Chrome version and locking it down, so it can't auto-update (It's like a wet eel though, 1 slip and poof, updated) Re: Custom Web Objects are opaque to TC? (TC11 + Angular) Chrome: Sys.Browser("chrome").BrowserWindow(1).Window("Chrome_RenderWidgetHostHWND", "Chrome Legacy Window", 1) Firefox:I can see elements, sort of, but... well, here is an example Sys.Browser("firefox").Page("http://itemmastertest.samtec.com/#/Dashboard").Panel(0).Panel(1).Panel(0).Panel(0). Panel(0).Panel(1).Panel(2).Panel(0).Panel("QueueItemMasterGrid").Panel(1).Panel(0).Panel(0).Panel(0).Panel(1). Panel(0).Link(0) IE Same as Firefox... Sys.Browser("iexplore").Page("http://itemmastertest.samtec.com/#/Dashboard").Panel(0).Panel(1).Panel(0).Panel(0). Panel(0).Panel(1).Panel(2).Panel(0).Panel("QueueItemMasterGrid").Panel(1).Panel(0).Panel(0).Panel(0).Panel(1). Panel(0).Link(0) Looks exactly the same...everything is buried in a sea of Panel(x)'s So, the solution, for me, is to NOT use Chrome. I guess this is where Alias'ing is going to come in REALLY handy.... Re: Cannot find any existing or open blank page in Firefox 40, Chrome 43 using Test Complete 11 You could launch the site with a script snippet Use something like Call Browsers.Item(btIExplorer).Run("http://www.google.com") followed by any BrowserWindow Object Methods you need (Maximize for example) Once the browser is up and running,(the .Run method) and the browser has navigated to the correct page(the optional navigation string) control will pass back to the Keyword test for further processing Re: Angular JS and Test Complet Yeah, what he said :) (Watching... same issue)