.only still runs all tests

[TDKRage]

experiencing issues when trying to do test.only.

I am running "jest --coverage". but it still executes all the tests and not the one specified as only

[cpojer]

Yes, that's because Jest parallelizes tests and other processes don't know whether test.only is used. When you use test.only, you should focus on the single test file you are testing, or pass it to Jest to only run that test. This is not going to change in Jest.

[edelgado]

Ooo.. how do we "focus on the single test file you are testing"? 🙂 I only know passing the file name to jest for the test that has it.only on it.

[jhbalestrin]

@cpojer I updated the docs and submitted a PR.
#5262

[brickfungus]

https://facebook.github.io/jest/docs/en/api.html#describeonlyname-fn
So is this not right?

[rickhanlonii]

@brickfungus PRs accepted to clarify that, similar to the clarification added here

[abanoubEssam]

you should skip others describe endpoints with describe.skip() its works form me , thats for more tests file , but you can use describe.only() if there is only one test file

[samlandfried]

Should .only be honored when running tests w/ --runInBand?

[cdimitroulas]

It should IMO, but it doesn't.

[manast-apsis]

this is one of the biggest show stoppers with jest, same problem as with ava. Yes, it is architectural very nice that every test file runs in its own process and in parallel, but at the end of the day it is a PITA to work with in a daily basis, specially with large code bases... Mocha gets this right, it has always done it, and for some reason all the major contenders fall short.

[ZYinMD]

Just use --watch, it'll only run tests files that have changed since last git commit, and won't repeat tests that have passed once.