Regression: test.only does not group skipped tests anymore

[tarjei]

🐛 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:

1. Choose a testcase
2. Annotate it with .only:

it.only("should print only one test", async () => {
await Promise.resolve(true)
}

3. 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.

[thymikee]

This behavior was changed in v23 if I remember correctly, so it works as expected.

[sheerun]

@thymikee I'm using 24.9.0 and it still shows skipped tests. Can you reopen?

[thymikee]

@sheerun If you have a minimal repro case we can download, please create a new issue and post there.

[sheerun]

@thymikee I don't get it. Author of this issue already posted issue and minimal repro that you can even run in browser

[thymikee]

It was changed with this PR: #8038 to fix #7999.
@SimenB do you think we should bring back grouping skipped tests and leave todo as is now?

[sheerun]

This issue happens in 24.9.0 which has been released in August while this PR has been merged in March.. It is a regression

[sheerun]

(it's happening not in verbose mode, but normal mode)

[sheerun]

Also my use case: I have 120 tests and have .only on just one of them. When running jest with default settings (also when using --watchAll), all 119 skipped tests are printed, instead of just one that interests me.

[thymikee]

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.

[sheerun]

Any chance to revert this change?

[nunofgs]

Any news here? just hit this as well. Very annoying.

[tralston]

I am seeing the same issue here, when I focus on a few tests out of dozens. Any updates?

[sheerun]

Happy yearversary of this issue everyone...

[github-actions]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 14 days.

[4ekki]

Still actual in 27.4.7

[lucasrmendonca]

Still an issue in 29.3.0

[github-actions]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.