--no-auto-watch and --auto-watch=false should be have the same about karma HOT 9 CLOSED

I can't reproduce this.

--no-auto-watch behaves the same as --auto-watch=false, it does not watch and therefore does not print "Watching..." logs

Agree, we might change "Watching..." logs to be debug rather than info.

from karma.

I can reproduce the issue easily with angular's test suite

from karma.

My output is totally the same:

$ testacular start angularFiles.js --no-auto-watch
info: Web server started at http://localhost:9876/

$ testacular start angularFiles.js --auto-watch=false
info: Web server started at http://localhost:9876/

from karma.

I have some config changes on my local branch but maybe it's single-run that must be used in addition with auto-watch?

this is how I run the tests when I see the difference:

testacular start testacular-jquery.conf.js --single-run --auto-watch=false

vs

testacular start testacular-jquery.conf.js --single-run --no-auto-watch

from karma.

yes, if I leave --single-run out, the two auto-watch flags behave the same.

from karma.

That's weird, I still can't reproduce it. Once you are in office, you show me...

from karma.

I think that the actual problem is that --single-run and --auto-watch=false puts testacular into auto watch mode (fs is being watched and testacular doesn't quit after the first run). that's also why the output is being printed.

from karma.

Ok, I finally managed to reproduce this. It's a bug in optimist https://github.com/substack/node-optimist/issues/71

Here's a pull request with a fix https://github.com/substack/node-optimist/pull/72

from karma.

This was merged and is in release v0.3.5 included. Will update the dependencies accordingly.

from karma.