Call for Chromedriver to stop when application is not running #933
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current
Application.stop
call looks like so:What this PR is requesting is to add in
chromedriver.stop()
to the above command. We've found many instances where the application crashes, but chromedriver remains open. Likely due to this call only verifying if the application is open or not before returning the promise. This leads to additional Electron instances spawning on subsequent test runs due to Chromedriver staying in the background.We've been running a local fork of this for the last year and have found this to be a reliable way to ensure that every service that's part of Spectron fully shuts down on a crash.