Open lane711 opened 3 months ago
What happens when you don't use waitFor(element)
, is there just a long delay to the next step or does the step fail?
You can also use await click(element,{waitForNavigation: false})
for Taiko to skip it's build in waits. or use setConfig({waitForNavigation: false})
to globally turn it off
different issues happen for example:
On Fri, May 3, 2024 at 10:57 AM DCoomer @.***> wrote:
What happens when you don't use waitFor(element), is there just a long delay to the next step or does the step fail?
You can also use await click(element,{waitForNavigation: false}) for Taiko to skip it's build in waits. or use setConfig({waitForNavigation: false}) to globally turn it off
— Reply to this email directly, view it on GitHub https://github.com/getgauge/taiko/issues/2724#issuecomment-2093501535, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBGCC4MXOQBZVQRZGR664LZAPFYHAVCNFSM6AAAAABHFYXJDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJTGUYDCNJTGU . You are receiving this because you authored the thread.Message ID: @.***>
Will be helpful if you can provide a sample or logs when you see the first issue.
I am trying to create e2e ui tests for a complex Angular-based app. Almost all user interactions have an API call, so there are delays with nearly every click event.
I'm using
waitFor
for many times. It seems to work 90% of the time but not 100%. The only way around this that I've found is to add explicit wait viaawait waitFor(3000);
before and after many interactions which is obviously not a good solution.I'm working on a large enterprise project and many other developers working with Taiko have had to implement similar workarounds.
Is there some technique we should be trying to eliminate the explicit waits?
Here are some lines of code that intermittently fail: