feat(test-runner): allow setting concurrency per browser #710
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 59b139c The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
LarsDenBakker
force-pushed
the
feat/per-browser-concurrency
branch
from
f6afd79
to
3990fed
Compare
LarsDenBakker
force-pushed
the
feat/per-browser-concurrency
branch
from
3990fed
to
59b139c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What I did
Concurrency can now be configured per browser launcher, for the chrome, puppeteer and playwright launchers.
Among other things, this is needed for firefox because it doesn't allow testing focus on tabs which are backgrounded. Setting a concurrency of 1 fixes that.
Fixes #238