When running cypress in UI mode, the terminal is filled up with requests similar to
GET /_/ 200 90.700 ms
How to stop cypress from printing all these requests to the terminal in the UI mode?
Run this command to open cypress in UI mode
cypress open 1>/dev/null
and this will keep your terminal empty from all these requests
Related
I have a VSCode config that will start the Firefox debugger server with -start-debugger-server, so that I can run an npm script and launch a website in my existing firefox windows without having to run a special firefox window with the debug server enabled.
Is there a way to turn the debugger server off short of re-starting Firefox? Something like a -stop-debugger-server CLI argument would be nice but there doesn't appear to be such a flag.
I've tried -stop-debugger-server, tried looking in the firefox CLI wiki, tried a web search. Stopped short of trying to re-start Firefox from the command line
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 am running my e2e tests in WebStorm console its all fine, no fails etc. but when I try to run them in mac Terminal its failing.
Currently I am using framework based on Protractor. When tests are running on system console all animations are like z-index is like 100 and rest of elements are under it, so WebDriver Protractor is unable to click them.
Any clues?
I checked printenv but it seems to be the same.
I'm trying to run jasmine unit tests on a CI server. To do that I have to launch a browser (FF in my case.)
I have a vnc server running on the server, so the browser has a display to attach to. However, when the browser is killed or terminated ungracefully (which can happen if a build fails), If I simply run "/usr/bin/firefox", I get a pop-up message from Firefox, and obviously the tests won't work.
Is there a set of flag I can use to always launch FF (as if it was a regular startup ?)
Note that :
/usr/bin/firefox -safe would not work, as it opens a popup to warn about safe mode
/usr/bin/firefox -P xyz would not work, as it opens a popup to define the profile
Thanks
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.