When a test fails, the stand alone web driver process is not shut down about gulp-angular-protractor

[ojengwa]

I am having a different weddriver issue. Not sure, could turn out to be a misconfiguration on my part... I have chromedriver setup globally on my dev machine but while trying to run the tests; I get the following error:

        throw new Error('Could not find chromedriver at ' +
        ^

Error: Could not find chromedriver at .../node_modules/protractor/selenium/chromedriver.exe
    at LocalDriverProvider.addDefaultBinaryLocs_ (.../node_modules/protractor/lib/driverProviders/local.dp.js:42:15)
    at LocalDriverProvider.setupEnv (.../node_modules/protractor/lib/driverProviders/local.dp.js:59:8)
    at Runner.run (.../node_modules/protractor/lib/runner.js:335:31)
    at process.<anonymous> (.../node_modules/protractor/lib/runFromLauncher.js:32:14)
    at emitTwo (events.js:87:13)
    at process.emit (events.js:172:7)
    at handleMessage (internal/child_process.js:686:10)
    at Pipe.channel.onread (internal/child_process.js:440:11)
[launcher] Runner Process Exited With Error Code: 1
[13:08:40] gulp-angular-protractor - Webdriver standalone server is stopped

I can run protractor on same directory with any issues. A hack would be to copy all requirements (chromedriver?) to the folder it's expecting it but I don't think that would scale... Did you encounter same problems? @jesperoastrom

Bernard.

[rochejul]

@jesperoastrom

I don't remember this case: probably when "autoStartAndStop" had to be manage into the gulp-stream.js ?

I will fix it

Many thanks for your feedback

[rochejul]

@ojengwa

Can your create a separated issue with a concret example (a zip file with your configuration)

Many thanks!