test: run system tests in parallel and fix collection name conflicts#7980
Open
test: run system tests in parallel and fix collection name conflicts#7980
Conversation
add71af to
77e84c6
Compare
This file contains hidden or 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
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.
Running system tests in parallel to speed up CI. This PR:
firestore.tsandtracing.tsthat caused conflicts when running tests in parallel on the same database.package.jsonto useconcurrentlyto run gRPC, REST, and named-db configurations in parallel.--parallelto mocha calls to run test files in parallel within each configuration.concurrentlytodevDependencies.