From Karma to Mocha, with a taste of jsdom

Re:From Karma to Mocha, with a taste of jsdom by ericclemmons on Tuesday November 24, 2015 @10:25AM (#10621205)

It seems that the majority of the benefit was replacing a browser instance (PhantomJS launched via Karma) with a virtual-DOM (jsdom).

Karma shines when you're running integration/e2e tests against _real_ browsers, especially IE.

[ Parent | on HN ]

Re:From Karma to Mocha, with a taste of jsdom by dmatteo on Tuesday November 24, 2015 @11:17AM (#10621599)

Integration tests are better handled on CI by test-automation tools like NightwatchJS or Capybara, imo.

Using Karma and Phantom for unit-testing it's just overhead to me.

[ Parent | on HN ]

Re:From Karma to Mocha, with a taste of jsdom by TheAceOfHearts on Tuesday November 24, 2015 @11:05AM (#10621475)

Have you tried Zuul [0]? It does a much better job at this than Karma.

If you want to run automated tests on every browser, you pick up a SauceLabs account, configure the simple zuul.yml file, and you're done. If you wanna run it locally, you run the zuul cli tool and open the link with that browser.

[0] https://github.com/defunctzombie/zuul

[ Parent | on HN ]