-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm run test-unit:watch
no longer supports focused tests
#36067
Comments
npm run test-unit:watch
no longer allows focus testsnpm run test-unit:watch
no longer supports focus tests
npm run test-unit:watch
no longer supports focus testsnpm run test-unit:watch
no longer supports focused tests
Isn't it related to the different test runner – Jest Circus – that is used with unit tests for some time? It's a new default starting from Jest 27 that we are going to update to quite soon anyway. Maybe this issue doesn't exist in Jest 27 anymore. We can test against #33287. I doubt it's anything on the |
I tried to reproduce this, following the outlined steps:
But it works for me (on trunk, using |
I can't reproduce this either. For me, it's correctly running only the tests I specified. @talldan Could you provide more info or maybe try it with a different setup? |
Oh, I think this is expected? |
Ah, ok, fair enough, didn't realise that. Seems like a bit of a useless feature, and I don't think it previously worked that way. |
I believe it always works that way though 😅 , or at least suppose to. I normally filter the files in watch mode if I only want to focus some of the tests. |
The test runner no longer seems to support changing a test to
describe.only
orit.only
.To reproduce:
npm run test-unit:watch
it.only
.only
, I noticed this while trying it ondescribe( 'undo'
- https://github.com/WordPress/gutenberg/blob/trunk/packages/core-data/src/test/reducer.js#L144)The text was updated successfully, but these errors were encountered: