Single test with parallel set to true

[kajalasharma]

When we set test_workers to true, all the tests run in parallel

But when we try to run a specific file using tag, it still runs the whole suite, it does not execute the other suites but a chrome instance is launched for all and 0 scenarios is displayed in the terminal output

[beatfactor]

I'm not sure I understand what is this about. Why run a single test with parallel set to true?

[kajalasharma]

Hi @beatfactor , so we want our project suite to run in parallel but then while automating a new test case we dont want to run the complete suite every time. So we use tags for each feature file we want to run. But here if i try to use tag to run a single feature file, it runs the complete suite.

[beatfactor]

But why not run the single test file directly instead?

[kajalasharma]

Yes we are exactly doing that. Running single test file by using tag

-- --tag @homepage

but instead the complete test suite gets executed.

[beatfactor]

can you share your config and the cli args that you're passing to the test runner?

[kajalasharma]

So just an update, i could make it work

I added

parallel: {
test_workers: {
enabled: true,
workers: 3,
}
}

in test settings and added the parallel in the scripts

"e2e-test:parallel": "npm run e2e-test -- --env parallel --report-path test/e2e/nw",

by which i will be able to run tests in parallel

when i want to run a single scenario using tag i can simple use a different script with tag name

"e2e-test:chrome": "npm run e2e-test -- --env chrome --report-path test/e2e/nw",