You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.
Our project has a lot of test suites. To avoid modifying all of them, we want to run specific tests separately "in band" while the rest can run in parallel. To accomplish this, I annotated a couple files with @group solo but all other files were not tagged at all.
I then ran this which seemed to work:
npx jest --group=solo --coverage=false --maxWorkers='1'
Only the specific tagged test suites were executed as desired. However, I then tried running this:
npx jest --group=-solo --coverage=true
I would have expected this to run all tests that are not tagged with "solo". Instead, everything was run including the tests with @group solo in them.
The text was updated successfully, but these errors were encountered:
Our project has a lot of test suites. To avoid modifying all of them, we want to run specific tests separately "in band" while the rest can run in parallel. To accomplish this, I annotated a couple files with
@group solo
but all other files were not tagged at all.I then ran this which seemed to work:
Only the specific tagged test suites were executed as desired. However, I then tried running this:
I would have expected this to run all tests that are not tagged with "solo". Instead, everything was run including the tests with
@group solo
in them.The text was updated successfully, but these errors were encountered: