testomatio
Shared run sometimes is not triggered
Describe the bug When TESTOMATIO_SHARED_RUN=1 parameter is set I expect to receive 1 test run when I have a few workers running tests in parallel, instead a few runs are created
To Reproduce Set up in package.json 2 scripts first one is abasic script for running tests, the second one is more parameterized version of the first one like this: "test:parallel": "TESTOMATIO=${TESTOMATIO_TOKEN} TESTOMATIO_URL=${TESTOMATIO_URL} TESTOMATIO_CREATE=1 cross-env HEADLESS=true codeceptjs run-workers 10 --plugins allure", "test:checkout": "TESTOMATIO_TITLE="E2E-checkout build:${BUILD_ID}" TESTOMATIO_SHARED_RUN=1 TEST_SUITE=checkout npm run test:parallel -- --grep '(?=.*@Checkout)'",
And trigger secondscript: npm run test:checkout
Expected behavior One test run should be generated
NOTE: sometimes a few test runs are created in case if env variable BUILD_ID was not passed and then test run title becomes E2E-checkout build: and we see a few runs like this in the testomat system
Screenshots
Desktop (please complete the following information):
- OS: Mac
- Browser chrome
- Version 19.0.6045.105
@DavertMik multiple runs are created when run multiple workers
to simplify the reproduction steps, run something like TESTOMATIO_SHARED_RUN=1 TESTOMATIO_TITLE='E2E-tests' npx codeceptjs run-workers 2
@DavertMik does TESTOMATIO_SHARED_RUN could be used only with start-test-run command?
