Even though my pattern only specifies tests that contain 2, tests that include 1 are included.
Judging from the behaviour, I think it's because sequentialTestGroup sets up a dependency of each child test tree on its preceding sibling.
Whilst this way of sequentialising tests works for running tests, it breaks the way tests are selected with --pattern causing more tests to run than necessary.
For the following test tree:
I try to filter by pattern:
Looks good. But then I run a second pattern:
Even though my pattern only specifies tests that contain
2
, tests that include1
are included.Judging from the behaviour, I think it's because
sequentialTestGroup
sets up a dependency of each child test tree on its preceding sibling.Whilst this way of sequentialising tests works for running tests, it breaks the way tests are selected with
--pattern
causing more tests to run than necessary.