Forum Discussion

dhundley's avatar
dhundley
Regular Contributor
2 years ago
Solved

same keyword test for browser based app sometimes displays objects, sometimes does not.

i have developed a testcomplete automation for one of our browser based applications. the start of every test case (12 in total, so far) utilizes the exact same keyword test that launches a chrome br...
  • JDR2500's avatar
    JDR2500
    2 years ago

    Although it doesn't address the root cause, I would be tempted to try to workaround the problem.  For instance, check if the Continue button is enabled after you populate the other fields.  If not clear the browser cache, reload the page and try the process again.  I'd do it in a loop that only tries again once or twice so you don't get stuck in it.

rraghvani's avatar
rraghvani
Icon for Champion Level 3 rankChampion Level 3
2 years ago

I remember seeing similar issues in version 14, but haven't seen it since. I'm current using v15.55.53.7.

If you watch your automation run, does the web page fully load? Do you have a delay mechanism, to wait for the web page to be fully loaded?

  • dhundley's avatar
    dhundley
    Regular Contributor
    2 years ago

    first, i am using the latest release of testcomplete/testexecute (15.67). 

    at your suggestion i tried implementing a page.Wait() operation immediately following the Run method that loads the URL and even added a manual 10 second delay after that.

    after my first two test cases completed successfully the third failed on the line highlighted in the image above with the indication that it was simply "unable to navigate to the page" of the URL. then, in my onstoptestcase event handler when i try to ensure that the browser window is closed if the test case has failed, it began doing this until the whole thing just stopped because of a recursive call to the handler. why does it say the object browser window does not exist when it is clearly being display on the screen? i'm open to any more suggestion you or anyone else might offer