How can I correctly run one single test from a file?

[riskoviv]

I write tests in TypeScript. When I try to run one single test or describe block by clicking on icon or right-click -> "Run test" on it, I've got this error in terminal:

testMatch, testPathIgnorePatterns and testRegex are have default jest config values, no changes made.

This error occurs regardless of jest.autoRun extension settings.
However running tests on saving a file works fine
I'm using these settings:

"jest.autoRun": {
   "watch": false,
   "onSave": "test-file"
}

and running tests by npm test works too.

I just want to be able to run tests individually, not only the whole test files. Do I need to change some settings or something else to make it work?

P.S.: I know that test.only exists, but I want to use the same feature provided by this plugin since it exists.

[connectdotz]

does your npm happen to be >= 7.0? If true, then this is a known issue, see #838, #852
You can find a few workarounds suggested here. Let me know if it works for you.

[riskoviv]

Okay, got it, my npm is 8.5.0. I think then I'll better just keep using test.only and describe.only for now (pretty useful feature btw). I see that the most appropriate solution for the issue is switching to yarn, but I can't do it right now.

[connectdotz]

@riskoviv added another workaround that might help - directly invoking the command to by-pass npm run, see the 3rd suggestion in the comment

[riskoviv]

I think this option value assumes using React, but I don't have react-scripts.cmd mentioned there because I'm not using React currently (and to be honest right now I'm working on educational project using just TypeScript w/o libraries).
But instead of it I set jestCommandLine option to node_modules\\.bin\\jest.cmd and now running single tests works perfectly. Thank you!

[connectdotz]

yup, you got the idea 👍 . Basically, just directly invoke whatever your package.json test script is doing with the jest.jestCommandLine setting to by-pass npm run.

[riskoviv]

By the way! If jest.jestCommandLine option value is empty (as it is by default), everything works correctly too. It looks like it didn't work correctly only if it had value npm test -- which I did set then (I forgot to mention this in the first message)