Name Mapping not working on remote browser
The name mapping and test cases work fine on local browsers, but would complain about page or object not found when running headless remote browsers and in parallel testing. I have the following se...
Forum Discussion
Something else stood out to me - are you running the headless tests on a remote machine?
No I'm not, currently I'm running it on local machine.
Eventually we want to integrate to Jenkins and trigger the tests from there so I'm trying to set it up.
I found the headless setup on this link: Creating and Running Web Tests in Headless Web Browsers With TestComplete
No I'm not, currently I'm running it on local machine.
Eventually we want to integrate to Jenkins and trigger the tests from there so I'm trying to set it up.
I found the headless setup on this link: Creating and Running Web Tests in Headless Web Browsers With TestComplete
I asked because you said "remote browsers" a couple of times and that's a different path for troubleshooting than this might be.
When you are running the headless test, does it fail on the very first object or does it work for a while and then eventually come up with an error?
When running on headless mode, our website redirects us to authentication page first, which works fine.
After authentication and when we're on the website for testing, it begins to fail on this line:
aqObject.CheckProperty(page.contentDocument.documentElement, "innerText", cmpContains, "Table Types")saying RuntimeError: Type mismatch.
The following line fails with "You are trying to call the "Click" method or property of an object that does not exist."
page.sideBar.FindChild("Id", VarToStr(featureNum)).Click()It also prompts me with:
"The NameMapping.Sys.browser.pagePivot2.sideBar object
can be found faster if you make //div[contains(@class, 'sidebar-menu-container')] the first selector in its selector list."
(This is already the first and the only selector in list, and clicking on the 'Improve Performance' only adds an empty selector before this one.)
And when I tried to click on a mapped button, it shows:
For which the "New Selectors" it's suggesting is wrong.
On headed browsers the tests execute fine without any problem.
