Node.js: re-run Mocha tests automatically on each source file change
What is the simplest way to tell Mocha to watch for source project files changes so that it can re-runs its tests?
node.js unit-testing mocha package.json
add a comment |
What is the simplest way to tell Mocha to watch for source project files changes so that it can re-runs its tests?
node.js unit-testing mocha package.json
Did my answer help solve your problem?
– James
Jan 25 at 4:28
add a comment |
What is the simplest way to tell Mocha to watch for source project files changes so that it can re-runs its tests?
node.js unit-testing mocha package.json
What is the simplest way to tell Mocha to watch for source project files changes so that it can re-runs its tests?
node.js unit-testing mocha package.json
node.js unit-testing mocha package.json
edited Nov 26 '18 at 0:38
jbarros
asked Nov 25 '18 at 23:51
jbarrosjbarros
428516
428516
Did my answer help solve your problem?
– James
Jan 25 at 4:28
add a comment |
Did my answer help solve your problem?
– James
Jan 25 at 4:28
Did my answer help solve your problem?
– James
Jan 25 at 4:28
Did my answer help solve your problem?
– James
Jan 25 at 4:28
add a comment |
1 Answer
1
active
oldest
votes
Run with the watch flag
mocha -w ./tests
And, if your test folder is called just test/
then you don't need to point out the folder (Mocha looks for changes in such folder by default), so you can end up just with:
mocha -w
this watches for test files changes, isn't it? I would like Mocha to observe my./src/**
files and, on each change, re-run the tests
– jbarros
Nov 26 '18 at 0:14
@jbarros the watch flag listens for changes in the CWD so as long as your source directory is included in that it'll re-run on changes to source code as well as tests. The file path dictates where mocha will find the test files in relation to the CWD.
– James
Nov 26 '18 at 0:24
thanks for your response. But I don't want mysrc
code insidetest
folder.
– jbarros
Nov 26 '18 at 0:34
@jbarros you don't have to, the CWD is determined by the terminal or whatever environment the CLI is executed under e.g. if your directory structure is./src
and./test
then the above should work exactly as you want because the CWD is.
– James
Nov 26 '18 at 1:29
Sorry for the delay. Yes, you are absolutely right. Thanks :-)
– jbarros
Feb 21 at 21:14
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53473182%2fnode-js-re-run-mocha-tests-automatically-on-each-source-file-change%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Run with the watch flag
mocha -w ./tests
And, if your test folder is called just test/
then you don't need to point out the folder (Mocha looks for changes in such folder by default), so you can end up just with:
mocha -w
this watches for test files changes, isn't it? I would like Mocha to observe my./src/**
files and, on each change, re-run the tests
– jbarros
Nov 26 '18 at 0:14
@jbarros the watch flag listens for changes in the CWD so as long as your source directory is included in that it'll re-run on changes to source code as well as tests. The file path dictates where mocha will find the test files in relation to the CWD.
– James
Nov 26 '18 at 0:24
thanks for your response. But I don't want mysrc
code insidetest
folder.
– jbarros
Nov 26 '18 at 0:34
@jbarros you don't have to, the CWD is determined by the terminal or whatever environment the CLI is executed under e.g. if your directory structure is./src
and./test
then the above should work exactly as you want because the CWD is.
– James
Nov 26 '18 at 1:29
Sorry for the delay. Yes, you are absolutely right. Thanks :-)
– jbarros
Feb 21 at 21:14
add a comment |
Run with the watch flag
mocha -w ./tests
And, if your test folder is called just test/
then you don't need to point out the folder (Mocha looks for changes in such folder by default), so you can end up just with:
mocha -w
this watches for test files changes, isn't it? I would like Mocha to observe my./src/**
files and, on each change, re-run the tests
– jbarros
Nov 26 '18 at 0:14
@jbarros the watch flag listens for changes in the CWD so as long as your source directory is included in that it'll re-run on changes to source code as well as tests. The file path dictates where mocha will find the test files in relation to the CWD.
– James
Nov 26 '18 at 0:24
thanks for your response. But I don't want mysrc
code insidetest
folder.
– jbarros
Nov 26 '18 at 0:34
@jbarros you don't have to, the CWD is determined by the terminal or whatever environment the CLI is executed under e.g. if your directory structure is./src
and./test
then the above should work exactly as you want because the CWD is.
– James
Nov 26 '18 at 1:29
Sorry for the delay. Yes, you are absolutely right. Thanks :-)
– jbarros
Feb 21 at 21:14
add a comment |
Run with the watch flag
mocha -w ./tests
And, if your test folder is called just test/
then you don't need to point out the folder (Mocha looks for changes in such folder by default), so you can end up just with:
mocha -w
Run with the watch flag
mocha -w ./tests
And, if your test folder is called just test/
then you don't need to point out the folder (Mocha looks for changes in such folder by default), so you can end up just with:
mocha -w
edited Feb 22 at 2:15
jbarros
428516
428516
answered Nov 26 '18 at 0:00
JamesJames
60.8k16120195
60.8k16120195
this watches for test files changes, isn't it? I would like Mocha to observe my./src/**
files and, on each change, re-run the tests
– jbarros
Nov 26 '18 at 0:14
@jbarros the watch flag listens for changes in the CWD so as long as your source directory is included in that it'll re-run on changes to source code as well as tests. The file path dictates where mocha will find the test files in relation to the CWD.
– James
Nov 26 '18 at 0:24
thanks for your response. But I don't want mysrc
code insidetest
folder.
– jbarros
Nov 26 '18 at 0:34
@jbarros you don't have to, the CWD is determined by the terminal or whatever environment the CLI is executed under e.g. if your directory structure is./src
and./test
then the above should work exactly as you want because the CWD is.
– James
Nov 26 '18 at 1:29
Sorry for the delay. Yes, you are absolutely right. Thanks :-)
– jbarros
Feb 21 at 21:14
add a comment |
this watches for test files changes, isn't it? I would like Mocha to observe my./src/**
files and, on each change, re-run the tests
– jbarros
Nov 26 '18 at 0:14
@jbarros the watch flag listens for changes in the CWD so as long as your source directory is included in that it'll re-run on changes to source code as well as tests. The file path dictates where mocha will find the test files in relation to the CWD.
– James
Nov 26 '18 at 0:24
thanks for your response. But I don't want mysrc
code insidetest
folder.
– jbarros
Nov 26 '18 at 0:34
@jbarros you don't have to, the CWD is determined by the terminal or whatever environment the CLI is executed under e.g. if your directory structure is./src
and./test
then the above should work exactly as you want because the CWD is.
– James
Nov 26 '18 at 1:29
Sorry for the delay. Yes, you are absolutely right. Thanks :-)
– jbarros
Feb 21 at 21:14
this watches for test files changes, isn't it? I would like Mocha to observe my
./src/**
files and, on each change, re-run the tests– jbarros
Nov 26 '18 at 0:14
this watches for test files changes, isn't it? I would like Mocha to observe my
./src/**
files and, on each change, re-run the tests– jbarros
Nov 26 '18 at 0:14
@jbarros the watch flag listens for changes in the CWD so as long as your source directory is included in that it'll re-run on changes to source code as well as tests. The file path dictates where mocha will find the test files in relation to the CWD.
– James
Nov 26 '18 at 0:24
@jbarros the watch flag listens for changes in the CWD so as long as your source directory is included in that it'll re-run on changes to source code as well as tests. The file path dictates where mocha will find the test files in relation to the CWD.
– James
Nov 26 '18 at 0:24
thanks for your response. But I don't want my
src
code inside test
folder.– jbarros
Nov 26 '18 at 0:34
thanks for your response. But I don't want my
src
code inside test
folder.– jbarros
Nov 26 '18 at 0:34
@jbarros you don't have to, the CWD is determined by the terminal or whatever environment the CLI is executed under e.g. if your directory structure is
./src
and ./test
then the above should work exactly as you want because the CWD is .
– James
Nov 26 '18 at 1:29
@jbarros you don't have to, the CWD is determined by the terminal or whatever environment the CLI is executed under e.g. if your directory structure is
./src
and ./test
then the above should work exactly as you want because the CWD is .
– James
Nov 26 '18 at 1:29
Sorry for the delay. Yes, you are absolutely right. Thanks :-)
– jbarros
Feb 21 at 21:14
Sorry for the delay. Yes, you are absolutely right. Thanks :-)
– jbarros
Feb 21 at 21:14
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53473182%2fnode-js-re-run-mocha-tests-automatically-on-each-source-file-change%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did my answer help solve your problem?
– James
Jan 25 at 4:28