Protractor test runs successfully, but fails to debug.
When ever I run the it launch the browser, and the fails.
Debugger listening on port 56547
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://10.129.19.134:51931/wd/hub
Process finished with exit code -1073741819 (0xC0000005)
Any Idea ?
Protractor version is 3.3.2
Selenium is 2.25.2
Yeahs I ran into the same issue and instead started using browser.pause(); in the code to debug
Related
I am getting 'Disconnected, because no message in 10000 ms' error while trying to run karma unit tests. This error triggered only after the installation of webdriver-manager ( to run protractor) and ran unit tests successfully before this installation.
I assumed that the error might be hitting since webdriver is up and running. So,I passed command 'webdriver-manager shoutdown' to stop it. but,it showed that no server is up and running.
My requirement is to run both protractor functional test and karma unit tests in same machine without any error.
Found the solution for this issue by myself.
Solution: Install angular cli using the command 'npm install -g #angular/cli'.
I am able to execute both karma unit tests and protractor functional tests in my system without any issue after installing angular cli.
I am working with envoy (https://github.com/envoyproxy/envoy). I got this project to build and debug on mac in VSCode using --spawn_strategy=standalone --genrule_strategy=standalone flags when I do bazel build.
However, when I try the same with bazel test, I can't get it to run without sandbox. When I run the command:
bazel test //:test_name --spawn_strategy=standalone --genrule_strategy=standalone
It runs the whole test and shows which tests passed and which ones failed.
But when I run the binary from /bazel-bin/ as ./test_name, it gives me an error saying: Caught Abort trap: 6, suspect faulting address. I am assuming this is because of some missing env variables created in sandbox - I have also tried just using --strategy=TestRunner=standalone. Is it possible to run it standalone? so that I can debug in an IDE such as VScode. Thank you!
In chrome tests runs fine, but I get this error every time I run my test in Firefox browser:
Failed: Error while running testForAngular: Document was unloaded [stack]
Error: Error while running testForAngular: Document was unloaded at executeAsyncScript_.then (C:\jenkins\workspace\QA-E2E-Firefox-Win10\automation\TestAutomation\SeleniumFramework\node_modules\protractor\built\browser.js:727:23)
I was able to fix this issue by using the selenium server to interact with the browser driver instead of protractor directly interacting with the browser driver, following changes has been made to my conf.js file.
directConnect: false,
seleniumAddress: 'http://localhost:4444/wd/hub'
I'm using a Windows 7 OS and trying to run a selenium webdriver test using python from my Eclipse+ PyDev IDE. I have downloaded the Google Chrome driver and added it to my path. I've also added the chromedriver.exe to C:\Python34\Scripts. I have tried the following:
from selenium import webdriver
driver = webdriver.Chrome()
I get the error message
selenium.common.exceptions.WebDriverException: Message: Can not connect to the 'chromedriver'
when I try to run my script. I've also tried the following:
driver = webdriver.Chrome(executable_path="C:\folder\chromedriver.exe")
I get a message saying file cannot be found. If I try the following from the terminal:
driver = webdriver.Chrome()
The browser is launched so it works from the terminal. The issue is running my script from Eclipse.
I work with this on Ubuntu but i came across the same kind of error, the problem was that i didn't have a sym-link to the chrome driver file,
In Ubuntu it is
sudo ln -s ~/selgrid/chromedriver /usr/local/bin/chromedriver
This might help
http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/
Good Luck!
Trying to run a Protractor test but am receiving the following command line error when trying to test in Chrome.
UnknownError: The process has not exited yet therefore no result is available ...
The test successfully runs in Firefox, i.e. when the protractor.conf.js file is set as such:
capabilities: {
'browserName': 'firefox'
}
I'm currently using ChromeDriver 2.10, which seems to have something to do with the issue (https://github.com/angular/protractor/issues/1424). However, I'm unclear how to configure Protractor to use a different version of ChromeDriver.
So, reverting to ChromeDriver 2.9 was as easy as downloading it from here (http://chromedriver.storage.googleapis.com/index.html?path=2.9/) and extracting the zip into /usr/local/lib/node_modules/protractor/selenium.
That fixed the immediate issue of not being able to run the test in Chrome. Still waiting on a fix for 2.10, I suppose.