jest -t 'some spec' still launches browser contexts for suites where no tests are run

[thernstig]

The following command jest -t 'some spec' still launches browser contexts for suites where no tests are run. This is unnecessary and bit unfortunate in the case where you run in headful mode.

Imagine you have one very specific test case like it('uploads file in the cool-app') and you run jest -t 'uploads file in the cool-app', but you have multiple test files. Then each test file will launch a browser context and then quickly close it, even though Jest will only execute one test case.

[mmarkelov]

I got some research on it and I don't have any ideas about it. We can't use runner to skip initial process. Also I tried to use environment for this. I also tried handleTestEvent, but the problem is that test skip event will run after beforeAll and beforeEach events

[thernstig]

Isn't there a way to get the test cases that will be run, inside the custom test environment? And you can check the length of it? It's possible that info is not available at that time?

[mmarkelov]

I just released next version, hope that i found out the way to skip it

[mmarkelov]

should be fixed in 1.6.0