Regression: test.only does not group skipped tests anymore
See original GitHub issue🐛 Bug Report
According to #2593 a .only on a test should remove the other tests from the test output.
To Reproduce
Steps to reproduce the behavior:
- Choose a testcase
- Annotate it with .only:
it.only("should print only one test", async () => {
await Promise.resolve(true)
}
- Run jest
Expected behavior
Only the single test should be in the output.
Link to repl or repo (highly encouraged)
https://repl.it/repls/NavajowhiteRemoteOutlier
envinfo
Ubuntu 18.04 , Node 10.16.3.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:16
Top Results From Across the Web
Skip tests conditionally · Issue #1626 · DevExpress/testcafe
I found a way to handle this but it's not scalable. I use this solution to skip over tests that require window resize,...
Read more >7. Incomplete and Skipped Tests — PHPUnit 9.5 Manual
This misinterpretation leads to the test reports being useless – you cannot see whether a test is actually successful or just not yet...
Read more >Tests not running in Test Explorer - visual studio
I have been working with the resharper test runner - which works fine. All tests are running, all tests are showing the right...
Read more >New mysql-test-run option to minimize skipped tests in ...
When a test or a test-suite is run with no-skip option, it ignores all the skip commands used within the test and forces...
Read more >Allure Framework
Allure Framework is a flexible lightweight multi-language test report tool that not only shows a very concise representation of what have ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Let’s reopen and discuss. I think changing the behavior for
test.skip
in #8038 was not necessary, also not requested in #7999. It was also an oversight from my side as a reviewer.Still actual in 27.4.7