When I run a suite of tests, Cypress is freezing on some tests. Different tests every time. At first I thought it was just tests that for some reason might take a while to run (like something that involves a timeout) but that doesn't seem to be the case. Running an individual test, with describe.only or it.only, does not freeze. Behavior is the same with cypress run in the command line.
When the test freezes, the spinner by the test in the Cypress pane still spins, but the app's UI is frozen -- for instance when my app's UI shows a spinner that spinner is frozen. Sometimes it even freezes on the VISIT / part of the test, before it even gets to any of the stuff that takes longer. Freezing happens in different spots, sometimes on different tests, on different cypress runs.
Also, even when a test file runs to completion, sometimes the Cypress UI (like the stop button at the top) doesn't respond.
This only started happening Friday, possibly coinciding with an update to 3.8.1. I've tried using 3.7.0 again, with no change.
Is anyone else experiencing this? I'm running on Windows 10 and the app is ReactJS.
If you are running Linux there is a bug related to Chrome 79 that freezes Cypress. Check here for more info: https://support.google.com/chrome/thread/24842699?hl=en
You can also update to latest Chrome version
How the problem was finally resolved ?
I encounter same problem but for some reason load event does not trigger even after 60.000ms; - I test app on different resolutions and sometimes, app doesn't load in some resolutions.
Related
Cypress (10.0.3) freezes when navigating to the particular page. The runner doesn't react at all. I can only force close it. Nothing unusual in the console.
The same happens when I do 'cypress run', test just freezes and never completes. And it happens in every environment (dev, staging, and prod).
I've been trying to use batch testing to test my luis app and have been experiencing an annoying bug. Basically the LUIS app page will become unresponsive while the batch testing window is open.
The most similar issue I've seen can be found here: LUIS web interface crashed after import JSON file for Batch Testing or Import App, with no answer yet.
My problem is also slightly different by the looks of it.
Experimenting has yielded the following results:
I can upload, test and view the results of 1 batch successfully sometimes. Sometimes the page will become unresponsive while I am looking at the results.
If I have successfully viewed the batch, but then close the batch testing window without deleting the batch, the next time I open the window the whole site will become unresponsive.
Recently opening the "Inspect" tab on the single utterance testing window has also begun making the page unresponsive.
I can submit images if needed, but the pages seem more or less the same after the bug has occurred, they simply stop working. Pressing buttons does nothing and I need to refresh the page if I want to get back to the bot's Dashboard/Build/Publish/Settings page.
The app has 18 intents, 12 entities, and a couple hundred utterances. I have tested it on a collaborator account and the bugs seems to occur there too. Not sure what other info might be relevant.
If anyone has experienced similar issues and can help I'd appreciate it. Being able to use the built in Batch Testing feature would be very useful.
I've got a Selenium test which crashes my browser (Firefox) whenever it runs. It's just a simple test (login, logout, login, logout, login ... crash) and I can't reproduce the crash when I do the same things manually, so I think the problem is with Selenium itself.
However, the issue could be that my Firefox starts with different options than when Selenium starts it. I could confirm that's not the case if I could start Firefox the exact same way Selenium starts it (eg. without plug-ins, with all history cleared, etc.) ... but I'm not sure how to do that.
Can anyone tell me which options to use to make Firefox run the same way as when Selenium runs it?
I was never able to find out how to emulate Selenium's use of Firefox. I tried using a fresh Firefox profile, but that still seemed to have differences from how Selenium ran Firefox.
Instead I wound up re-writing my test to be two tests, and then it was able to log in/out twice in the first test and once in the second test, avoiding the issue I was trying to debug (which only manifests when I try to log in/out 3 times in the same test).
If anyone can provide a better explanation of how to emulate Selenium's running of Firefox I'd be happy to accept that answer.
I have a proprietary application for automated testing that I built here at work that uses Selenium WebDriver classes to test our applications. It uses Firefox, but sometimes, when a new browser is launched, Firefox will open in Safe Mode and display the Safe Mode dialog. This seems to happen completely randomly, i.e. I will set up twenty tests to run and at any point this might happen. There only one block code that can be executed from test to test to launch a new browser, so it isn't in the testing application. Is there a way to override, or bypass, the safe mode dialog when this happens?
I need to run regressions overnight a lot of the time and it's frustrating when I see that my tests have been hung because of this
I have some SeleniumWebdriver/TestNG tests that Im successfully running on FireFox. If I am watching the tests run, it is okay.
But If I start using another browser in the meanwhile, or skype for example, and I go back to the FireFox window that is running the tests, I always find out that some error has occurred - for example, the "User name" input hasnt been filled out.
Why does this happen, and how can I prevent it?
Try to use driver.switchTo().window(driver.getWindowHandle()); when filling out the form.