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).
Related
For the web app that I am automating (cloud.redhat.com/openshift), I am working in a "preserve all cookies" mode:
Cypress.Cookies.defaults({
preserve: /.*/, // match-all regexp
});
When I run my script - it correctly dismisses the accept cookies dialog that pops up right on the start, and proceeds to feeding in the login credentials. So far so good - but then the accept cookies dialog pops up a 2nd time :(, and this time Cypress doesn't dismiss it and gets stuck because the dialog covers the whole page.
Another peculiarity is that this problem doesn't happen when I run the script from the development environment, when I use "cypress open". It only happens when running the script from the command line, when I use "cypress run". The problem can be recreated in development as well if I switch from Chrome to Firefox. Why is there a difference between the behaviors when using "cypress open" and "cypress run", and when using a different browser? How can I dismiss or prevent the dialog from popping up a 2nd time? We're on Cypress 7.7, but I also tried recreating the problem in Cypress 10 and it happens there too.
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.
In a React Native project, I have some breakpoints (in Google Chrome DevTools).
I then decide to deactivate them and switch the "Activate Breakpoints" button to "blue" color:
...which works (no breakpoints are triggered while I continue running the application).
However, when I reload the application the breakpoints do trigger despite the "non-activated" flag exists:
This should not be happening.
The only way to ignore the breakpoints is:
- Activate them again
- Press F8 to continue
- Deactivate them
(then, the application continues running without breakpoints).
Is this a known bug? Do you also experience it and if yes is there any solution to this?
Thank you!
RN developer tools are still in testing phase. For MAC they are more stable than comparing to windows. The reason is actually the bundling of assests and js files.
the console takes it as a single file and then distributes it to different files that are showing in the workingdebugger.js file.
So it recreates them every time you reload the app.
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.