Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Watch command #73

Closed
dazld opened this issue Apr 4, 2014 · 10 comments
Closed

Watch command #73

dazld opened this issue Apr 4, 2014 · 10 comments
Assignees
Labels
feature New functionality or improvement

Comments

@dazld
Copy link

dazld commented Apr 4, 2014

Would like a simple way to watch the test folder for changes, and re-run when something is updated.

I guess it'd be simple to wrap this call around something and come up with a DIY solution, but would be great if it was built in.

@hueniverse
Copy link
Contributor

This does not make sense for a test runner.

@toymachiner62
Copy link

Mocha has this feature and it's great b/c I do not have to have a grunt task to watch the file. I can just call $ mocha my-test.js -w and it automatically watches the file for changes. 👍

@hueniverse hueniverse self-assigned this Apr 14, 2015
@chrisinajar
Copy link

This is a very very useful feature for anyone doing TDD. A lot better than cmd+s, alt+tab, up, enter... 👍

@ghost
Copy link

ghost commented Jun 3, 2015

How about using fsmonitor?

@chrisinajar
Copy link

There are a hundred tools to do it, I'm using nodemon personally, but why not just build it in with a flag? Since most people are coming from the mocha world, matching their feature set isn't a bad objective.

Lab solves so many problems for you, and then just has this 1 random broken window where you have to solve it yourself. It'd be different and I would understand if the project philosophically aimed to be unopinionated, but that's not the type of project this is.

@ghost
Copy link

ghost commented Jun 3, 2015

Why would you implement something that can already be done using tools that
specialize in solving this particular requirement? I personally prefer to
keep my choice of tool when I change my test runner ...
On Jun 3, 2015 7:36 PM, "Chris Vickery" notifications@github.com wrote:

There are a hundred tools to do it, I'm using nodemon personally, but why
not just build it in with a flag? Since most people are coming from the
mocha world, matching their feature set isn't a bad objective.

Lab solves so many problems for you, and then just has this 1 random
broken window where you have to solve it yourself. It'd be different and I
would understand if the project philosophically aimed to be unopinionated,
but that's not the type of project this is.


Reply to this email directly or view it on GitHub
#73 (comment).

@AdriVanHoudt
Copy link
Contributor

you can run fsmonitor -s -p '+*.js' npm test and I'll do the trick for you, you can even put that in a npm command like npm run watch

@Marsup
Copy link
Contributor

Marsup commented Jun 3, 2015

If you use gulp/grunt/... like all the kids these days, it also already does that for you.

@dazld
Copy link
Author

dazld commented Jun 4, 2015

please lock this, it was an off the cuff thought, and repo owners have already replied.

solution: can use any of the myriad task runners as @Marsup mentions.

@Marsup Marsup added feature New functionality or improvement and removed request labels Sep 21, 2019
@lock
Copy link

lock bot commented Jan 9, 2020

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature New functionality or improvement
Projects
None yet
Development

No branches or pull requests

6 participants