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.

Sign up for GitHub

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

Jump to bottom

Karma autoWatch blocks grunt watch #3

Closed
artyomtrityak opened this issue Mar 25, 2013 · 5 comments
Closed

Karma autoWatch blocks grunt watch #3

artyomtrityak opened this issue Mar 25, 2013 · 5 comments

Comments

@artyomtrityak
Copy link

The main problem now that if i run Karma not in singleRun it blocks grunt watch.
But if i run in singleRun it starts and stops browsers after each file change.

In 0.6.x versions Testacular / grunt-testacular plugin allows run watch mode for grunt and watch for Testacular so browsers are not stopping.

Thanks!
@artyomtrityak
Copy link
Author

prev discussion #3 and dignifiedquire/grunt-testacular#9

@vojtajina
Copy link
Contributor

I would recommend using Testacular/Karma watching rather then grunt watch
and calling karma run. The first way is way more efficient and therefore
faster.

On Mon, Mar 25, 2013 at 9:20 AM, Artyom Trityak notifications@github.comwrote:

prev discussion #3 https://github.com/karma-runner/grunt-karma/issues/3and
dignifiedquire/grunt-testacular#9dignifiedquire/grunt-testacular#9

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-15403425
.

@geddski
Copy link
Contributor

geddski commented Mar 29, 2013

I plan to add this feature, I've wanted it myself. But @vojtajina has a good point. Here's an example of the autoWatch option he's talking about.

@artyomtrityak
Copy link
Author

@vojtajina i understand your point but running all in one terminal window looks fine for me.

dignifiedquire added a commit to dignifiedquire/grunt-karma that referenced this issue Mar 30, 2013
@dignifiedquire
feature: Add keepalive option.
e947fb1 
If keepalive is set to false, then this allows grunt to run other tasks
after the karma task has been started to run.
The default is set to true, so this will not break existing
installations.
This fixes karma-runner#3 and karma-runner#4.
@dignifiedquire dignifiedquire mentioned this issue Mar 30, 2013
Closed
@geddski
Copy link
Contributor

geddski commented Apr 1, 2013

background: true option added in 0.4.0. Thanks!

@geddski geddski closed this as completed Apr 1, 2013
@jeme jeme mentioned this issue Apr 3, 2013
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vojtajina @geddski @artyomtrityak