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

No stdout option #1314

Closed
simonzack opened this issue Feb 17, 2015 · 6 comments
Closed

No stdout option #1314

simonzack opened this issue Feb 17, 2015 · 6 comments

Comments

@simonzack
Copy link

I'm doing karma start and karma run in the same process. Both print the test results to stdout, which is rather annoying. Can there be an option to disable runner.js's stdout?

I'm monkey-patching http.request right now which is rather ugly.

@freethejazz
Copy link
Contributor

I would just redirect the output of one of the two processes to /dev/null. That would look like:

karma start > /dev/null

This is a pretty standard "unixy" way of dealing with output of programs and is quite powerful. For more info on this approach, look for resources explaining stdout redirection in linux (that's what the > is for)

@simonzack
Copy link
Author

I'm running both on the same process.

@freethejazz
Copy link
Contributor

I'm not an expert on these things, but my understanding of a process is that is a running instance of some program. By that definition, karma start and karma run are two separate instances of a running program and would thus each have their own process.

How are you running the two commands?

@simonzack
Copy link
Author

I'm using the api. karma.server.start and karma.runner.run.

@simonzack
Copy link
Author

I ended up doing the ajax request myself, which was reasonably simple. The runner api is rather lacking. The throws couldn't be caught either.

@dignifiedquire
Copy link
Member

The node api was never designed to be feature complete. If you have concrete suggestions please file a new issue and/or feel free to submit a PR with the methods you are looking for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants