-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add option to exit automatically #13
Comments
I came here to request this. :) I don't think it should be limited to headless though, it would be nice to run and exit on any supported browser. |
@bclinkinbeard 👍 Good idea, not sure why I thought it would only be useful in headless. Will change description to be more clear. |
Awesome! Though 1.6 isn't published according to npm. |
sorry, just published now :) |
Awesome, thanks! Not to keep being a pest, but shouldn't the browser be closed at the end as well? Right now the test process exits but the browser remains open. |
you're right, we also need to kill the browser process (it actually does in linux). Any ideas on it? |
I only glanced at the code but it looked like browser-launcher passes the process to cb, so would guess it could be killed that way? On Sat, Apr 26, 2014 at 2:40 PM, Azer Koçulu [email protected]
|
The |
https://github.com/juliangruber/tape-run uses https://github.com/juliangruber/browser-run under the hood, which works to close the browser on my system. Maybe look for a solution there? |
Hmm, tape-run only successfully closes PhantomJS for me. Chrome and Safari stay open, but even Phantom doesn't close for me with prova. |
@bclinkinbeard phantom should be closed if you pass -q, may be it should be default. but I don't have an answer to the other question, I'll ask this in browser-launcher repo |
Ah, duh. :) I think there is something "off" with my system that prevents browsers from being closed. Feel free to close this issue. |
I would love an option for prova to automatically exit when it gets the test results from a browser. This would let me run prova automatically on every commit in a continuous integration server, and could be useful for running browser tests with
npm test
, which most people are used to.Maybe something like
prova test.js -b -l chrome -q
, which would launch chrome to run the tests. When the test results are received, prova would kill chrome and exit with status code of zero if the tests succeeded and non-zero if the tests failed.Currently it is very close to being able to use in a CI environment for browser tests, but not quite without being able to exit automatically.
The text was updated successfully, but these errors were encountered: