I am getting the following error in Azure Devops pipeline when running the protractor tests.
How can i fix this ?
enter image description here
You should comment the selenium address in your config file. Then it will work.
// seleniumAddress: 'http://localhost:4444/wd/hub', It is connecting to the local connection hence not working
Related
using Maven Testng and Build is successful on Eclipse local machine but when the same was run on azure pipeline it shows error no such element and element not interactable
When i am trying to do UI automation testing in AWS Code build getting this error
Error: ECONNRESET socket hang up
at ClientRequest. (node_modules/selenium-webdriver/http/index.js:294:15)
I am using standalone selenium docker for firefox inside AWS Code build with linux environment.
Same script is working in local machines
Please verify selenium running on port 4444
I am executing Selenium test cases on a remote machine using microsoft VSTS release pipeline "Run Powershell on target machine", this powershell script is running properly on local machine, but when trying to execute on remote machine, always getting the error, "Starting ChromeDriver 2.32.498550 (9dec58e66c31bcc53a9ce3c7226f0c1c5810906a) on port 42936, only local connections are allowed"
Please let me know how to resolve the issue.
I'm struggling to get TFS 2015 to run my selenium specflow tests. The automation is for our production environment so the TFS project doesn't need to deploy the website code, it just needs to run the automation agaist www. (The automation code has the www address coded into it)
I've seen the chrome driver sandbox parameter although that hasn't removed my problem. I've added the following when initializing my chrome driver, shown below
Use of chrome sandbox
var options = new ChromeOptions();
options.AddArguments("–no-sandbox"); // also tried "--no-sandbox"
return new ChromeDriver(options);
TFS Command line build step settings
Tool: packages/NUnit.ConsoleRunner.3.6.1\tools\nunit3-console.exe
Arguments: "../../../My.Automation/bin/Debug/My.Automation.dll" --where "cat=demo
Working folder: $/UAT Automation/Dev/SourceCode
Error experienced on TFS (it works locally on my machine)
I get the same error when I run the command on the server myself.
Unknown error: cannot find chrome driver
Few ideas:
Check repository. Probably you didn't checkout folder with chrome
driver (you have it locally, but not in repo)
You have a path to chrome driver in code, and it is different from the path in TFS server
I am trying to configure a Selenium testing through Bamboo. I am able to run Selenium scripts directly from command line, however it always fails if I run it through Bamboo remote agent. The error is:
: Could not start Selenium session: Failed to start new browser session: Error while launching browser
at com.thoughtworks.selenium.DefaultSelenium.start(DefaultSelenium.java:107)
I took some advice from the web, and checked "Allow service to interact with desktop" for Bamboo remote agent service. However, it does not work.
Anyone have other suggestions?
You must run Bamboo in Console Mode for this to work. Also, the build machine desktop must be active - and not covered or minimized if you want mouse simulations to work. I know right!