-
Notifications
You must be signed in to change notification settings - Fork 214
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
Can we speed up our Nightwatch tests by running them in PhantomJS ? #39
Comments
A quick read of the Wiki page: https://github.com/nightwatchjs/nightwatch/wiki/Running-tests-in-PhantomJS |
Just a tip: I've been using |
@nelsonic don't know if it will be a big speedup though. They're both WebKit-based browsers. But the simplicity of test setup alone justifies it in my opinion |
@jedwards1211 thanks very much for reminding us about http://webdriver.io But good to hear that you are having success with it. |
Heh, fair point...I'm confused though, ghostdriver doesn't have any badges at all ;) |
@jedwards1211 yeah, the situation with
|
hahaha nice 😄 But you can't do integration tests with karma, can you? |
@nelsonic (i'm like 2 years late in this thread) Have your tried running your nightwatch tests in a HEADLESS manner? the test execution will be crazy fast. |
On a reasonably "mature" project, e.g: https://github.com/TheScienceMuseum/collectionsonline we are running several end-to-end test scenarios: https://github.com/TheScienceMuseum/collectionsonline/tree/master/test/client
Running all of these tests takes 3 Minutes on
localhost
and 4.28 minutes on Travis-CI e.g: https://travis-ci.org/TheScienceMuseum/collectionsonline/builds/172018586#L3263Can we investigate using PhantomJS instead of Chrome to reduce the amount of time that it takes to run our tests?
Starting point: https://github.com/nightwatchjs/nightwatch/wiki/Running-tests-in-PhantomJS
The text was updated successfully, but these errors were encountered: