Watch mode improvements for browser runner #9968
Merged
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.
Proposed changes
It turns out that there is a race condition when Mocha tries to start the test without the worker process being ready and initialised. This patch is an attempt to fix that.
fixes #9612
fixes #9608
Types of changes
Checklist
Further comments
Missing for this to land:
find a better approach to auto trigger or wait for the browser runner: if we let the browser runner trigger the framework to start, we loose the ability to re-run tests through hot reload (e.g. due to changes to the component)let's add smoke tests to ensure we test watch capabilitiescreated new issue for it: [🐛 Bug]: Add smoke tests for watch mode #9974Reviewers: @webdriverio/project-committers