New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testcase hangs after expecting in two different windows. Testcafe V1.12 Chrome 89. #6037
Comments
Thank you for your report. Unfortunately, I cannot reproduce the issue with the version from the Git repo. Could you please install
or by using the following line in your
and check if the problem can be reproduced with this version and your machine? |
Hi, I tried with alpha 1.12.1 version. Also fails. However, I found that the issue might be when running this tests with my When I remove my testcafe config file the test doesnt hung anymore. Can you please try if running the previous tests with the next
|
Thank you for sharing your config file. I was able to reproduce the issue. It seems that it is caused by video recording options: the test passes when I remove them from the config file. |
@AndreyBelym Any updates regarding the issue? Is there any chance that it will be picked up and fixed soon? |
No updates yet. Once we get any results, we will post them in this thread. |
What is your Test Scenario?
Running a test that requires interaction with two windows and expecting in two windows.
What is the Current behavior?
The tests hangs if expecting in both windows with Chrome.
What is the Expected behavior?
Finish the test result.
What is your web application and your TestCafe test code?
Running testcafe on website that requires access. However I replicated this issue on a public website.
The issue comes when expecting in two different windows. If the new created window did not had any expect the tests result would finish. However if both windows are expected the tests hangs when expecting in the main or parent window.
Your Environment details:
The text was updated successfully, but these errors were encountered: