When I run GUI tests (Selenium, Java. Launched from IntelliJ idea on Ubuntu 16.04).
Each new test opens a new chrome browser (and close it when the test finishes) in the foreground, stilling the focus from what ever I am doing.
I can't run headless or change the tests to only launch a single browser and do clean up from test to test.
Any way to tell chrome to launch in the background? any relevant flag? If not maybe some way to tell Ubuntu to move Chrome to the background?
Solutions are welcomed, thanks!
Related
I'm new to Cypress and recently started implementing e2e tests for our system. A peculiarity of this system is that the authentication happens on a popup window.
I've already successfully created a simple test that loads the site, waits for the authentication to complete and then asserts that the page title is shown. This test runs without errors using the cypress client (cypress open), but when I run it in headless mode (cypress run --headless) the test fails.
When I see the video from the headless run, I don't see the popup window appear like it does when I run it with the GUI. Has anyone else had an issue like this where popup windows don't show on headless mode?
I also found this bug on the Chromium site related to issues displaying popup windows in headless mode, so it might be related to that, but the bug appears as closed.
I'm using Cypress 6.1.0 and Chrome 87
Thanks in advance for any help.
This was being caused by an issue with the integration of my website with another service that for some reason only occurred on headless mode. After fixing that, it works ok.
How does Puppeteer handle PWA installation? Can I just assume that no installation will take place?
I searched for "puppeteer pwa" but could not find any info.
Puppeteer is really a tool for testing an application. It is a headless browser and therefor would not offer any real way to test or simulate the installation flow.
The service worker should register and the initial life cycle should trigger. However it is headless, which means state is not preserved. So you are more or less doing an InCognito session each test run.
I am trying to run UI tests on Selenium. The website runs on SSL. When using Chromedriver, after login, the page keeps on loading and shows "Establishing secure connection" and then eventually times out. Chrome also shows the yellow triangle before the URL in the browser. However, I don't see the yellow triangle when I log into the website using Chrome outside of this. I further noticed that the standard settings in Chrome are not the same as the Chrome instance that opens up when Chromedriver fires it, not sure why.
Can someone tell me what might be going on here and how I can fix the issue?
It may be chromedriver issue. Try to downgrade it. Version 2.12 helped us with similar problem.
https://sites.google.com/a/chromium.org/chromedriver/downloads
I was using Ripple Chrome extension for test running my phonegap apps, and I did all settings for Ripple, like making a Chrome shortcut with --allow-file-access-from-files and in Chrome extension list checking "allow local file access" for Ripple.
On running my HTML file which I made for phonegap build, Chrome is taking a good time to deliver a response. Everything is working, the only issue is the delay on response.
I tried on another desktop, and there it is quiet and fast. I re-installed the extension and restarted Chrome and OS a couple of times to no effect.
For your information, I had similar issues when using Chrome. Make sure Chrome isn't running in the background when you close it. Since a few versions of Chrome, this is enabled by default. Check your taskbar to see if this is the case.
If Chrome is indeed running in the background, right-click on the chrome-icon in the taskbar and disable "running in background". This worked for me and now Ripple fires superfast.
You probably need to confirm your system spec. development workstations are known to be resource demanding, particularly the RAM, and processors. if your app was faster on another system, you might want to check that system's spec also and compare with yours.
Running selenium tests using chrome driver, everytime the browser starts up I'm getting a notification balloon about added persistent background apps and then the test hangs it doesn't even appear to time out.
Anyone else seeing similar issues?