Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Unable to connect to chromedriver in Bitbucket Pipeline

Feldhacker June 1, 2018

I am trying to get Cucumber/Selenium working in Bitbucket Pipelines.  I have the chrome webdriver installed and available on the path, but when I execute cucumber I receive the error:

"unable to connect to chromedriver 127.0.0.1:9515 (Selenium::WebDriver::Error::WebDriverError)"

Ideas?

1 answer

0 votes
Peter Plewa
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 16, 2018

Hi @Feldhacker,

It is possible to run Selenium in Pipelines, could you share your bitbucket-pipelines.yml?

Issue is likely related to the docker image you are using and it's configuration, perhaps https://medium.com/@yiquanzhou/run-selenium-ui-tests-in-docker-container-78be98e1b52d would guide you to a solution?

Thanks,

Peter

Deleted user January 27, 2022

Hi Peter,

 

I appreciate this is some time ago but maybe you could help me?

 

I'm trying to get the similar issue here working.

 

It looks when my script in the pipeline tried to execute:

'driver = new ChromeDriver(GetChromeOptions());'

I get these two errors: 'Connection refused [::ffff:127.0.0.1]:33859 (localhost:33859)'

OpenQA.Selenium.WebDriverException : Cannot start the driver service on http://localhost:33859/

 

Any advice if you see this would be appreciated :)

 

 

My .yml is:

image: mcr.microsoft.com/dotnet/sdk:5.0
pipelines:
default:
- step:
services:
- selenium-standalone
script: # Modify the commands below to build your repository.
- export PROJECT_NAME=Swoop-Acceptance
- export TEST_NAME=Swoop-Acceptance
- dotnet restore
- dotnet build $PROJECT_NAME
- dotnet test $TEST_NAME

definitions:
services:
selenium-standalone:
image: selenium/standalone-chrome:latest
port: 4444

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events