我的测试文件有一个类似于/something.test的结构。并命令NPX cypress run——spec path/something.test。JSX在终端中给出了以下异常:

Can't run because no spec files were found.
We searched for any files matching this glob pattern:
...

令人惊讶的是，下面的工作和运行测试正好为一个文件(提供你已经安装了jest):

jest path/something.test.jsx

有多种方法可以实现这一点。

你可以添加。only到它或描述见@bkucera答案 你可以从终端做，在这里的文件解释 NPX cypress run——record——spec "cypress/integration/my-spec.js" NPM run cypress -- --record——spec "cypress/integration/my-spec.js"

通过终端运行特定文件:

 npx cypress run --record --spec "cypress/integration/my-spec.js"

 npm run cypress -- --record --spec "cypress/integration/my-spec.js"

我的测试文件有一个类似于/something.test的结构。并命令NPX cypress run——spec path/something.test。JSX在终端中给出了以下异常:

Can't run because no spec files were found.
We searched for any files matching this glob pattern:
...

令人惊讶的是，下面的工作和运行测试正好为一个文件(提供你已经安装了jest):

jest path/something.test.jsx

A very easy solution is to prefix your tests in with numbers, as testing frameworks will typically will run tests in alpha/numeric order by default - so if I have to check one spec file - I will copy the contents into a file 0-[file-name].spec and re-run the test command. Once the test completes - you terminate the test run - as you will have the results you were looking for. This answer is targeted at projects where your testing framework is abstracted and as a developer, you do not have all available options for your testing framework. Not the best answer, but it works and is intuitive and super easy to do. I have found this to be a way to avoid adding a bunch of conditional skips() or only() calls that will not make it to production, will have to be removed and you can easily add the file pattern to .gitignore file so these local files do not get checked in.

您可以像这样运行测试。

运行——spec **/file.js