KBC-587 parallel tests #448
Draft
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
romanbracinik
approved these changes
Jul 16, 2020
|
Jak pustit: |
zajca
force-pushed
the
zajca-kbc-587-phpunitupdate
branch
from
634296e to
988cdbf
Compare
zajca
force-pushed
the
zajca-kbc-587-phpunitupdate
branch
from
e2ec48f to
8ee1853
Compare
|
Změnil sem ten PR, parallelní testy mají vlastní namespace, je přesunutá jde to pustit takto: je předtím potřeba vyexportovat envy postup by byl asi takový:
|
|
|
|
Změnil sem ten PR a asi bysme to měli probrat na team callu, takže vracám na review @keboola/team-connection a dávám PR jako draft. |
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.
JIRA: https://keboola.atlassian.net/browse/KBC-587
parallelní testy mají vlastní namespace, je jako example přesunutá BucketsTest do tests/Parallel/Backend/Common
jde to pustit takto: je předtím potřeba vyexportovat envy source ./set-env.sh
docker-compose run --rm dev vendor/bin/paratest tests/Parallel/Backend/Common -p 16 --functionalpostup by byl asi takový:
nasetujeme projekt pro každý backend
začnem přesouvat testy do parallel, když to jede přesunout pokud nějaký test padá nechat v původní test classe a vyřešit v budoucnu, moc sa stým nedrbat.