Skip to content
This repository has been archived by the owner on Feb 11, 2021. It is now read-only.

Launch/detect ChromeDriver for local testing #244

Closed
scottgonzalez opened this issue Nov 19, 2015 · 1 comment
Closed

Launch/detect ChromeDriver for local testing #244

scottgonzalez opened this issue Nov 19, 2015 · 1 comment
Assignees
@arschmitz
Milestone
0.4.2

Comments

@scottgonzalez
Copy link
Contributor

We should detect if ChromeDriver is running before trying to run local functional tests. If it's not running, we should try to start it. If anything fails, we should provide instructions on how to proceed.
@jzaefferer jzaefferer mentioned this issue Nov 19, 2015
Closed
@csnover
Copy link
Contributor

csnover commented Nov 19, 2015

Please see theintern/digdug#19 which is a feature enhancement request to automate this for all projects that use Intern

arschmitz added a commit to arschmitz/PEP that referenced this issue Dec 3, 2015
@arschmitz
Build: Add grunt-selenium-standalone
b432c2b 
Allows installation and starting of selenium standalone and chrome driver
from grunt

Fixes jquery-archivegh-244
@arschmitz arschmitz mentioned this issue Dec 3, 2015
Closed
arschmitz added a commit to arschmitz/PEP that referenced this issue Feb 4, 2016
@arschmitz
Build: Add grunt-selenium-standalone
97d9ef8 
Allows installation and starting of selenium standalone and chrome driver
from grunt

Fixes jquery-archivegh-244
@scottgonzalez scottgonzalez added this to the 0.4.2 milestone Sep 27, 2016
@snyk-bot snyk-bot mentioned this issue Nov 14, 2019
Open
@X-oss-byte X-oss-byte mentioned this issue Sep 11, 2024
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@arschmitz arschmitz

Labels
None yet
Projects
None yet
Milestone
0.4.2
Development

No branches or pull requests
3 participants
@scottgonzalez @csnover @arschmitz