Node.js: re-run Mocha tests automatically on each source file change












1















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







share|improve this question

























  • Did my answer help solve your problem?

    – James
    Jan 25 at 4:28
















1















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







share|improve this question

























  • Did my answer help solve your problem?

    – James
    Jan 25 at 4:28














1












1








1








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







share|improve this question
















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 26 '18 at 0:38







jbarros

















asked Nov 25 '18 at 23:51









jbarrosjbarros

339313




339313













  • 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





Did my answer help solve your problem?

– James
Jan 25 at 4:28












1 Answer
1






active

oldest

votes


















0














Run with the watch flag



mocha -w ./tests





share|improve this answer
























  • 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 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













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
});


}
});














draft saved

draft discarded


















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









0














Run with the watch flag



mocha -w ./tests





share|improve this answer
























  • 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 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


















0














Run with the watch flag



mocha -w ./tests





share|improve this answer
























  • 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 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
















0












0








0







Run with the watch flag



mocha -w ./tests





share|improve this answer













Run with the watch flag



mocha -w ./tests






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 26 '18 at 0:00









JamesJames

60.2k16120194




60.2k16120194













  • 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 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





















  • 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 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



















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




















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







-

Popular posts from this blog

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Image
0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{...
Read more

Calculate evaluation metrics using cross_val_predict sklearn

Image
1 In the sklearn.model_selection.cross_val_predict page it is stated: Generate cross-validated estimates for each input data point. It is not appropriate to pass these predictions into an evaluation metric. Can someone explain what does it mean? If this gives estimate of Y (y prediction) for every Y (true Y), why can't I calculate metrics such as RMSE or coefficient of determination using these results? python scikit-learn cross-validation share | improve this question edited Nov 28 '18 at 17:52 desertnaut 20.3k 7 43 79 ...
Read more

Insert data from modal to MySQL (multiple modal on website)

Image
0 I have problem with inserting data to MySQL from modal. My modal: <a href="#" class="badge badge-pill badge-success">6 komentarzy</a> <a href="#" class="badge badge-pill badge-danger">brak komentarzy</a> <a data-toggle="modal" href="#add_desk_comm_{$desk_['desk_id']}" data-target="#add_desk_comm_{$desk_['desk_id']}" class="ediiit">(dodaj)</a> <div class="modal fade" id="add_desk_comm_{$desk_['desk_id']}" tabindex="-1" role="dialog" aria-labelledby="edit_printer" aria-hidden="true"> <div class="modal-dialog" role="document"> ...
Read more