# karma

http://karma-runner.github.io/0.10/index.html

# what it is ?

A test runner for js tests. Can ran tests described with a lots of frameworks (Jasmine, Mocha, QUnit, ...)

# Karma config file

http://karma-runner.github.io/0.10/config/configuration-file.html

# Browsers config

http://karma-runner.github.io/0.10/config/browsers.html

export CHROME_BIN=/usr/bin/google-chrome-stable

# IntelliJ integration

http://mariuszprzydatek.com/2013/07/21/angularjs-karma-and-debugging-unit-tests-in-webstorm-or-intellij-idea/

# karma & grunt

Use grunt-karma npm module.

A sample grunt task is needed :

karma: {
  unit: {
      configFile: 'karma.conf.js'
  }
}

1
2
3
4
5

karma.conf.js should be generated with the karma command line tool.

Install launcher, karma-chrome-launcher to use Chrome, or karma-phantomjs-launcher for a silent execution.

# karma & phantomjs

A big number of tests can cause phantomjs to crash, it is worse with a coverage preprocessor.

There is nothing to do instead of using something else or split the tests suites into several pieces, but coverage tools needs the tests to be ran to work ...

https://github.com/karma-runner/karma-phantomjs-launcher/issues/55

https://www.quora.com/What-behavior-have-you-seen-from-PhantomJS-that-differs-from-that-of-a-mainstream-non-headless-browser

https://stackoverflow.com/questions/24436460/phantomjs-dies-by-high-memory-consumption

# phantomjs

phantomjs could be considered dead :

phantomjs repo issues

mailing list

[Announcement] Stepping down as maintainer

headless chrome alternative