-
Notifications
You must be signed in to change notification settings - Fork 708
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
Mocha unit testing with PhantomJS #120
Comments
I tried, but didn't manage to get it working. How about Karma? |
Not a big fan, but I don't like Mocha either, so why not. |
What's wrong with Mocha? I don't mind Karma being used either. |
@addyosmani probably mostly personal preference, but; it's bloated, slow, introduces implicit globals, awful programmatic API, too short default timeout, too much boilerplate to use it on the client-side, and probably more I can't remember right now. |
@sindresorhus Which one do you use? I had bad experience with Mocha also, so I switched to Jasmine + Karma. I can implement that combo if that works for you guys. |
Mocha |
:) |
Just tried to integrate it and it's a PITA. I'm also +1 for Mocha though. |
👍 Mocha. |
What do you guys think about this kind of setup for testing with PhantomJS & Mocha? Users would be able to easily switch browsers or use external services like Sauce Labs, Browerstack etc. Or is it a tad too opinionated? |
I was also unable to get gulp-mocha-phantomjs to work. I raised this https://github.com/mrhooray/gulp-mocha-phantomjs/issues/47 issue. This plugin seems easier to use than Karma, although Karma does provide code coverage too as an added bonus. |
WebdriverIO is a great Nodey way to test, so that's probably the right way to go. I'm already quite experienced with it, I'm just waiting for it to release a public API for plugins. |
https://github.com/mrhooray/gulp-mocha-phantomjs
The text was updated successfully, but these errors were encountered: