When using Edge and concurrency no steps are executed on test
franciscolosardo opened this issue · comments
I was unable to run a test in Edge on saucelabs with concurrency ON. It gets up to the fixture page , and it doesnt execute even the first action on the webpage.
When running just one file remotely from my mac it works. Its very slow but at least it works.
Would you please clarify the number of concurrent sessions? Have you tried to decrease this number?
I tried 4 concurrent tests which execute 4 different tests on parallel.
And i also tried just 1 test. The latter worked.
It seems to be a problem with concurrency in edge.
Could you please try to execute two concurrent tests?
Turns out this happened today with concurrency 2 again.
One thing to note is if i grab a saucelab's instance running the test and refresh the page , the test starts without problems! So there seems to be a problem when the page first loads or something.
I just opened one of the running tests, clicked on the browser, clicked refresh and test started running.
@franciscolosardo
I was not able to reproduce the issue, but anyway thank you for additional information. At this moment the cause of the issue is unclear. It seems that it can be not related to SauceLabs, however, it's difficult to say precisely.
We'll try to research the issue, however, I can not give any estimates on this.
Another tip :
i used the following way of initializing my tests after i got the problem with concurrency ,
i created a promise with an instance of testcafe for each one of my tests as the file im attaching.
As this still gave me the exact problem i checked how i initialized my tests, turns out i did it this way :
I fixed the problem later by changing how my tests ran, following way was implemented. Note i added a client function that reloads the webpage 5 seconds after loading before running any tests, this fixed the issue..
I'm really liking what testcafe is bringing to the table in terms of functionality and i'm trying my best to give back to the community and developers , please try and see if you can replicate the issue and ,if not, just keep in mind if anyone else faces it how to workaround it.
best of luck with this!
Thank you for the additional information. We need some time for researching and debugging this issue.
This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.
We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.