Hi,
Recently we have one of our test cases that failed consistently but at different test steps when running with IE on cloud run, when run it locally, sometime it'll pass, other time it got stuck. All other browsers seemed to have no problem passing this test case. Also manual IE operation is okay. Can you please help to find out what's going on and how we can avoid getting test failed alert with IE cloud runs?
Thank you!
Hi Dazhen,
Could you please provide more information as follows:
1. What are the error messages that you are seeing?
2. The title of the post contains 'possibly due to timing'. Could you please elaborate on that?
3. By 'Manual IE Operation', do you mean manually doing the steps on the browser?
4. Does it affect several test cases, or only the one in the snapshot?
Regards,
Subject7 Team
Hi Joseph,
1 and 2, In general the reasons are step timeout, although this can happen at varies steps. For exact reason, I was hoping you can take a look at the reason by referencing test run numbers posted in my screen shot.
3. I can manually operate IE to perform the test scenario, and the UI seems to be working okay.
4. Currently it affect only one test case, we have other test cases failing with IE seemingly at random before, but after a few days, the same test cases without changes would pass no problem.
It appears that IE does not like the XPath that works on Chrome on the same step. IE has a different engine that is deprecated (Officially ending in June 2022) and hence it's difficult to support it. My recommendation is to use alternative XPath's and see which one can be used with IE.
One tip is to use "descendant" and not "//" in the XPath. For example:
//div[@id='confirmActionModal']//h5[contains(text(),'Delete Note')] --> //div[@id='confirmActionModal']/descendant::h5[contains(text(),'Delete Note')]. Or just to test this theory, use absolute XPath to the element: /html/body..../h5.
Please sign in to leave a comment.