feat(tests): support paratest #1721
Open
Conversation
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
aazsamir
force-pushed
the
feat/paratest
branch
from
8a7e204 to
20f524b
Compare
aazsamir
force-pushed
the
feat/paratest
branch
from
20f524b to
20547af
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Use with
./vendor/bin/paratestinstead of./vendor/bin/phpunit4min20s -> 50s
So now, tests have custom internalStorage set per worker. Paratest guarantees to set unique TEST_TOKEN.
Tests that modify files MUST use unique names for them (or use lock).
There were some kinda random errors due to container being statically set, so on tests
tearDownI'm setting it tonull.