Thank you for sharing the error details for the test execution.
Your assumption about the splash screen seems to be the correct one as of our perspective as well. However, here are few suggestions, which you may give a try to.
The first thing to try will also prove if our assumption is correct - please include as a first step in the test an execution delay
. At the beginning you can start with a larger timeout and then decrease it step by step to find out its optimal value. If the test passes successfully that way, it is the splash screen that causes the misbehavior.
Wait on elements
You mentioned that you have attempted to fix the misbehavior with Wait on elements - is this the wait steps
that you have tested? I guess this is what you have used and this is the other possible option, which is also not hard-coded as the delay, which pauses the execution.
Though, you mentioned this didn't help as well. So, there is another idea I have.
Test Studio uses global project timeouts
which can be easily accessed in the Test ribbon. However, for cases like the current one, the default 15 seconds may not be sufficient for certain steps. Therefore, each verification step (wait and extract, as well) has its own WaitOnElement property
. By default this is greyed out and will be enabled once the UseStepWaitOnElementsTimeout
Please, give a try to the above suggestions and let me know, if any of these is useful to cover the specific application behavior.