Since moving from a Linux VM to a Macbook Pro for testing, I have been having a recurring issue running Protractor automation.

At a certain point in my suite all, a Java application called GridLauncher pops up. Selenium was already running prior to this as tests were running and passing, but if I kill this Java app I kill the entire Selenium process. This occurs if I start Selenium manually or if I let Protractor start an instance itself.

The app popping up coincides with my tests failing, which then throws off the test workflow and causes subsequent tests to fail.

This only occurs on Mac and has been reproducible by 2 people on the team so far.

  • I installed webdriver-manager that seems to use a different verison of GridLauncher (it appears as GridLauncherV3) and the problem dissapeared.
    – Sergio Cia
    Mar 10 '17 at 8:37
  • This happens to me allllllll the time.
    – uchuugaka
    Apr 7 '18 at 10:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.