Stability problems of recordings

[fleipold]

Good morning,

Were now using ranorex for a month and we still have huge stability problems when executing the recordings.
We encounter a log of problems with not found elements and more "wait for" and "exists2 expressions do not solve the problem for us. We modified the xpath elements to make them more stable but it did not help. The elements normally can be found via the spy afterwards

Can you suggest some more measurements we can perform to figure out why the elements where not found during runtime ? Because currently we need to invest way to much time in getting the tests stable than actually writing any tests

Regards Florian

[odklizec]

Hi Florian,

I'm afraid, without knowing more details about your tests, exact errors you are getting, recorded xpaths and AUT as such, there is not much anyone here can do or suggest. Any chance you can post at least snapshot (NOT screenshot) of typically failing element, report with recorded error and example of failing recording (at least screenshot)? These could help us better understand your problem.

[fleipold]

Hello,

Is it possible to get a better error result when a element cannot be found ?
Because currently we only get the information that it could not be found. But checking the xpath the element can be found.
Is there option to get the status of the site at the time when the error occurred ? Any more information about what actually did happen ?

Because its no solution for us to raise a error report each time one of the element which worked for the last five times no suddenly fails.

Regards Florian

[Stub]

Waiting for repository items to exist and not exist has been key to my tests. In fact I was just analysing one failure just now where it changed the wrong item but validated the correct item. The test failed because the correct item hadn't been changed. This suggested to me a timing issue, so I have added some WaitForExists to ease it towards the correct item.

I frequently do something, wait for the next thing to happen, do something more, wait for that thing to no longer exist before proceeding.

[fleipold]

Believe me that we added a "wait for" for the items which where not found during testing. But even waiting for 30s for the item often does not change anything.
Its also not the same item which is failing. You can execute the test on one machine, its failing, youre adding "wait fors" and "delays" for the items and its working, then you run it on another machine and its failing again. Sometimes for the same and sometimes for other items.

And the only information we get is that the element is not available. Checking the xpath it is. So what can i additionally do to get more information about what is going on ? Just adding "wait fors" and "delays" for good measurement is more guessing that actually addressing the specific problem.

[Support Team]

Hi Fleipold,

May I ask you to send an email directly to [email protected] with a detailed description of your problem?
We could do a remote session if it is necessary.

I'm looking forward to your email.

Sincerely,
Matthias