blocks|key|562463|text|对于更改测试目录，这似乎不是什么“容易”的支持。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|562464|然而，也许你应该看看this+issue，相对于你的问题。|offset|length|562465|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/visionmedia/mocha/issues/341^0|0|A|A|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

This doesn't seem to be any "easy" support for changing test directory. 
However, maybe you should take a look at <a href="https://github.com/visionmedia/mocha/issues/341" rel="nofollow">this issue</a>, relative to your question.

blocks|key|562550|text|这里有一种方法，如果你的测试文件夹中有子文件夹，例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|562551|/test
/test/server-test
/test/other-test|code-block|syntax|javascript|562552|然后，在linux中，您可以使用find命令递归列出所有*.js文件，并将其传递给mocha：|562553|mocha+$(find+test+-name+'*.js')|562554|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Here's one way, if you have subfolders in your test folder e.g.

<pre><code>/test
/test/server-test
/test/other-test
</code></pre>

Then in linux you can use the find command to list all *.js files recursively and pass it to mocha:

<pre><code>mocha $(find test -name '*.js')
</code></pre>

blocks|key|562589|text|不要使用-g或--grep选项，该模式对其中的测试名称进行操作()，而不是对文件系统进行操作。当前的文档在这方面是误导性的和/或完全错误的。要将整个命令限制为文件系统的一部分，您可以传递一个模式作为最后一个参数(它不是一个标志)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|562590|例如，此命令会将您的报告器设置为spec，但只会直接测试server-test目录中的js文件：|562591|mocha+--reporter+spec+server-test/*.js|code-block|syntax|javascript|562592|此命令将执行与上面相同的操作，另外，它将只运行测试的it()字符串/定义以“Fnord：”开头的测试用例：|562593|mocha+--reporter+spec+--grep+"Fnord:"+server-test/*.js|562594|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Don't use the -g or --grep option, that pattern operates on the name of the test inside of it(), not the filesystem. The current documentation is misleading and/or outright wrong concerning this. To limit the entire command to a portion of the filesystem, you can pass a pattern as the last argument (its not a flag).

For example, this command will set your reporter to spec but will only test js files immediately inside of the server-test directory:

<pre><code>mocha --reporter spec server-test/*.js
</code></pre>

This command will do the same as above, plus it will only run the test cases where the it() string/definition of a test begins with "Fnord:":

<pre><code>mocha --reporter spec --grep "Fnord:" server-test/*.js
</code></pre>

blocks|key|562671|text|我使用的是Windows7，使用的是node.js+v0.10.0、mocha+v1.8.2和npm+v1.2.14。我只是想让mocha使用path+test/unit来找到我的测试，在我花了很长时间尝试了几件事之后，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|562672|使用"test/unit/*.js“选项在windows上不起作用。有充分的理由，windows+shell不会像unixen那样扩展通配符。|562673|但是，使用"test/unit“确实可以，不需要文件模式。例如："mocha+test/unit“运行test/unit文件夹中的所有文件。|562674|这仍然只运行一个文件夹文件作为测试，但您可以传递多个目录名作为参数。|562675|此外，要运行单个测试文件，您可以指定完整路径和文件名。例如："mocha+test/unit/mytest1.js“|562676|我实际上在package.json中设置了npm“脚本”：{+"test"："mocha+test/unit“}，|562677|所以“npm+test”运行我的单元测试。|562678|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

I am on Windows 7 using node.js v0.10.0 and mocha v1.8.2 and npm v1.2.14.
I was just trying to get mocha to use the path test/unit to find my tests,
After spending to long and trying several things I landed,

Using the "test/unit/*.js" option does not work on windows.
For good reasons that windows shell doesn't expand wildcards like unixen.

However using "test/unit" does work, without the file pattern.
eg. "mocha test/unit" runs all files found in test/unit folder.

This only still runs one folder files as tests but you can pass multiple directory names as parameters.

Also to run a single test file you can specify the full path and filename.
eg. "mocha test/unit/mytest1.js"

I actually setup in package.json for npm 
 "scripts": {
 "test": "mocha test/unit"
 },

So that 'npm test' runs my unit tests.

blocks|key|562738|text|使用以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|562739|mocha+server-test|code-block|syntax|javascript|562740|或者，如果您有子目录，请使用以下命令：|562741|mocha+"server-test/**/*.js"|562742|请注意双引号的使用。如果省略它们，您可能无法在子目录中运行测试。|562743|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Use this:

<pre><code>mocha server-test
</code></pre>

Or if you have subdirectories use this:

<pre><code>mocha "server-test/**/*.js"
</code></pre>

Note the use of double quotes. If you omit them you may not be able to run tests in subdirectories.

blocks|key|346777|text|我刚才遇到了这个问题，通过删除--recursive选项(我已经设置了)并使用上面建议的相同结构解决了它：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|346778|mochify+"test/unit/**/*.js"|346779|这将为我运行/test/unit/下所有目录中的所有测试，同时忽略/test/中的其他目录|346780|entityMap^0|F|B|0|0|R|0|6|B|X|6|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|K|$]]

I had this problem just now and solved it by removing the <code>--recursive</code> option (which I had set) and using the same structure suggested above:

<code>mochify "test/unit/**/*.js"</code>

This ran all tests in all directories under <code>/test/unit/</code> for me while ignoring the other directories within <code>/test/</code>

blocks|key|562855|text|正如@superjos在注释中提到的，使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|562856|mocha+--recursive+"some_dir"|offset|length|style|CODE|562857|entityMap^0|0|0|S|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

As mentioned by @superjos in comments use

<code>mocha --recursive "some_dir"</code>

blocks|key|346911|text|运行test_directory中的所有文件，包括与test.js匹配的子目录|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|346912|find+./parent_test_directory+-name+'*test.js'+%7C+xargs+mocha+-R+spec|code-block|syntax|javascript|346913|或者使用--recursive开关|346914|mocha+--recursive+test_directory/|346915|entityMap^0|2|E|Q|7|0|0|4|B|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

Run all files in <code>test_directory</code> including sub directories that match <code>test.js</code>

<pre><code>find ./parent_test_directory -name '*test.js' | xargs mocha -R spec
</code></pre>

or use the <code>--recursive</code> switch 

<pre><code>mocha --recursive test_directory/
</code></pre>

blocks|key|347000|text|正如@jeff-dickey建议的那样，在项目的根目录下，创建一个名为test的文件夹。在该文件夹中，创建一个名为mocha.opts的文件。现在我试图改进Jeff的答案，对我有效的不是指定一个测试文件夹的名称，而是指定一个模式，通过添加以下行来查找要在我的项目中运行的所有测试：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|347001|mocha.opts中的*/tests/*.js+--recursive|347002|如果您想要指定在其中查找测试的确切文件夹，我做了如下操作：|347003|shared/tests/*.js+--recursive
server/tests/graph/*.js+--recursive|code-block|syntax|javascript|347004|我希望这能帮助那些比其他答案更需要帮助的人。|347005|entityMap^0|Z|4|1L|A|0|0|A|C|O|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|13|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|14|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|R|$]]

As @jeff-dickey suggested, in the root of your project, make a folder called <code>test</code>. In that folder, make a file called <code>mocha.opts</code>. Now where I try to improve on Jeff's answer, what worked for me was instead of specifying the name of just one test folder, I specified a pattern to find all tests to run in my project by adding this line:

<code>*/tests/*.js --recursive</code> in <code>mocha.opts</code>

If you instead want to specify the exact folders to look for tests in, I did something like this:

<pre><code>shared/tests/*.js --recursive
server/tests/graph/*.js --recursive
</code></pre>

I hope this helps anyone who needed more than what the other answers provide

blocks|key|347063|text|最好的方法是在package.json中添加一个“测试”npm脚本，该脚本使用正确的参数调用mocha。这样，您的package.json也可以描述您的测试结构。它还避免了其他答案中的所有这些跨平台问题(双引号与单引号，"find“等)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|347064|要让mocha运行"test“目录中的所有js文件：|347065|"scripts":+{
++++"start":+"node+./bin/www",+--+not+required+for+tests,+just+here+for+context
++++"test":+"mocha+test/**/*.js"
++},|code-block|syntax|javascript|347066|然后，为了只运行冒烟测试，调用：|347067|npm+test|347068|您可以通过这种方式标准化所有项目中所有测试的运行，因此当新的开发人员开始处理您的项目或其他项目时，他们知道"npm+test“将运行这些测试。这在历史上有很好的先例(例如，Maven，大多数老式的"make“项目也是如此)。当所有项目都有相同的测试命令时，它肯定有助于CI。|347069|类似地，您可能有一个更快的“冒烟”测试的子集，您可能希望mocha运行：|347070|"scripts":+{
++++"test":+"mocha+test/**/*.js"
++++"smoketest":+"mocha+smoketest/**/*.js"
++},|347071|347072|npm+smoketest|347073|另一种常见的模式是将您的测试放在与它们测试的源文件相同的目录中，但将测试文件命名为*.spec.js。例如:+src/foo/foo.spec.js测试src/foo/foo.js。|347074|按照约定运行所有名为*.spec.js的测试：|347075|++"scripts":+{
++++"test":+"mocha+**/*.spec.js"
++},|347076|然后调用以下命令来运行所有测试：|347077|npm+test|347078|看到这里的模式了吗？好的。:)一致性击败了mura。|offset|length|347079|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Mura_(Japanese_term))^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|L|4|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1I|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1J|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1K|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1L|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|1M|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1N|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1O|8|@]|9|@]|A|$G|H]]|$1|S|3|J|5|6|7|1P|8|@]|9|@]|A|$]]|$1|T|3|U|5|F|7|1Q|8|@]|9|@]|A|$G|H]]|$1|V|3|W|5|6|7|1R|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1S|8|@]|9|@]|A|$]]|$1|Z|3|10|5|F|7|1T|8|@]|9|@]|A|$G|H]]|$1|11|3|12|5|6|7|1U|8|@]|9|@]|A|$]]|$1|13|3|14|5|F|7|1V|8|@]|9|@]|A|$G|H]]|$1|15|3|16|5|6|7|1W|8|@]|9|@$17|1X|18|1Y|1|1Z]]|A|$]]|$1|19|3|-4|5|6|7|20|8|@]|9|@]|A|$]]]|1A|$1B|$5|1C|1D|1E|A|$1F|1G]]]]

The nice way to do this is to add a "test" npm script in package.json that calls mocha with the right arguments. This way your package.json also describes your test structure. It also avoids all these cross-platform issues in the other answers (double vs single quotes, "find", etc.) 

To have mocha run all js files in the "test" directory:

<pre><code>"scripts": {
 "start": "node ./bin/www", -- not required for tests, just here for context
 "test": "mocha test/**/*.js"
 },
</code></pre>

Then to run only the smoke tests call:

<pre><code>npm test
</code></pre>

You can standardize the running of all tests in all projects this way, so when a new developer starts on your project or another, they know "npm test" will run the tests. There is good historical precedence for this (Maven, for example, most old school "make" projects too). It sure helps CI when all projects have the same test command.

Similarly, you might have a subset of faster "smoke" tests that you might want mocha to run:

<pre><code>"scripts": {
 "test": "mocha test/**/*.js"
 "smoketest": "mocha smoketest/**/*.js"
 },
</code></pre>

Then to run only the smoke tests call:

<pre><code>npm smoketest
</code></pre>

Another common pattern is to place your tests in the same directory as the source that they test, but call the test files *.spec.js. For example: src/foo/foo.js is tested by src/foo/foo.spec.js.

To run all the tests named *.spec.js by convention:

<pre><code> "scripts": {
 "test": "mocha **/*.spec.js"
 },
</code></pre>

Then to run all the tests call:

<pre><code>npm test
</code></pre>

See the pattern here? Good. :) Consistency defeats <a href="https://en.wikipedia.org/wiki/Mura_(Japanese_term)" rel="noreferrer">mura</a>.

blocks|key|563266|text|windows中的另一种选择是使用cross-env包并遵循package.json中的npm脚本|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|563267|"scripts":+{
++++"test":+"cross-env+mocha+'*.test.js'"
++},
"devDependencies":+{
++++"cross-env":+"latest",
}|code-block|syntax|javascript|563268|在这种情况下，根文件夹中模式为*.test.js的所有测试文件都将由mocha运行。|563269|entityMap^0|H|9|U|C|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Another option in windows could be using <code>cross-env</code> package and following npm script in <code>package.json</code>
<pre><code>&quot;scripts&quot;: {
 &quot;test&quot;: &quot;cross-env mocha '*.test.js'&quot;
 },
&quot;devDependencies&quot;: {
 &quot;cross-env&quot;: &quot;latest&quot;,
}
</code></pre>
In this case all test files with pattern *.test.js in root folder will be run by mocha.

<a href="http://visionmedia.github.com/mocha/" rel="noreferrer">Mocha</a> tries to find test files under <code>test</code> by default, how do I specify another dir, e.g. <code>server-test</code>?

How to specify test directory for mocha?

单元测试

文件系统

默认情况下，会尝试在test下查找测试文件，如何指定另一个目录，例如server-test

问如何指定mocha的测试目录？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何指定mocha的测试目录？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何指定mocha的测试目录？
EN