https://jestjs.io/docs/cli#--testnamepatternregex

你的测试是这个文件my。test。js

test("My Sum", () => {
  const sum = 3;
  expect(sum).toBe(3);
});

以测试名在CLI上运行

jest -t Sum

使用npm测试与regex匹配部分文件名的例子:my.test.js

npm test -t my

以下是我的看法:

./node_modules/.bin/jest --config test/jest-unit-config.json --runInBand src/components/OpenForm/OpenForm.spec.js -t 'show expanded'

注:

./node_modules/.bin/... is a wonderful way, to access the locally installed Jest (or Mocha or...) binary that came with the locally installed package. (Yes, in your npm scripts you can jest with nothing before, but this is handy on command line... (that's also a good start for your debugging config, whichever IDE you are using...) Your project might not have a set of configuration options. But if it does (peek into the scripts in package.json), this is, what you need. --runInBand – as said, don't know about your configuration, but if you concentrate on developing/fixing a single test, you rather do not want to deal with web workers... Yes, you can give the whole, explicit path to your file Optionally, you can use -t to not run all tests in that file, but only a single one (here: the one, that has something with ‘show expanded’ in its name). Same effect can be achieved by glueing .only() into that file.

在Visual Studio Code中，这让我只能运行/调试一个带有断点的Jest测试:在Visual Studio Code中调试测试

我的发射。Json文件里面有这个:

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Jest All",
      "program": "${workspaceFolder}/node_modules/.bin/jest",
      "args": ["--runInBand"],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "windows": {
        "program": "${workspaceFolder}/node_modules/jest/bin/jest",
      }
    },
    {
      "type": "node",
      "request": "launch",
      "name": "Jest Current File",
      "program": "${workspaceFolder}/node_modules/.bin/jest",
      "args": ["${relativeFile}"],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "windows": {
        "program": "${workspaceFolder}/node_modules/jest/bin/jest",
      }
    }
  ]
}

在package.json文件中:

  "scripts": {
    "test": "jest"
  }

要运行一个测试，在该测试中，将test(或it)更改为test。只有(或it.only)。若要运行一个测试套件(多个测试)，请将describe更改为description .only。 如果需要，可以设置断点。 在Visual Studio Code中，转到调试视图(Shift + Cmd + D或Shift + Ctrl + D)。 从顶部的下拉菜单中，选择笑话当前文件。 单击绿色箭头以运行该测试。

我发现最快/最简单的方法是用

npx 是 TheNameOfYourFile

此外，您可以“订阅”以继续阅读更改

npx 是 TheNameOfYourFile --watchAll

只是一个小插件，因为如果使用。/node_modules/.bin/jest -i…或者只是开玩笑-我…或者NPM测试-我…

如果你在全局安装了jest(如npm install -g jest)，那么只调用jest就可以了，这是一种不太干净的处理依赖关系的方式 如果Jest只安装在包的本地，并且想调用Jest脚本而不需要绕道npm脚本，你可以使用npx Jest -i…=>这正是NPX的目的。它可以节省编写。/node_modules/.bin/....的时间

如果你把jest作为脚本命令运行，比如npm test，你需要使用下面的命令让它工作:

npm test -- -t "fix order test"