feat(config): allow configurable launchers, preprocessors, reporters

[vojtajina]

karma.configure({
  reporters: ['progress', 'html_coverage'],
  browsers: ['Chrome', 'my_chrome']
  preprocessors: {
    '**/*.coffee': ['coffee_bare']
  }
});

karma.defineLauncher('my_chrome', 'Chrome', {
  flags: ['--start-maximized']
});

karma.definePreprocessor('coffee_bare', 'coffee', {
  options: {
    bare: true
  }
});

karma.defineReporter('html_coverage', 'coverage', {
  ...
});

The reason, why I decided for this solution, rather than inlining (as proposed in #317) is that this solution allows using these custom launchers/reporters from CLI. It also makes it easier to create only a single instance of a preprocessor (if the configuration is the same).

In addition to defining/configuring custom reporters/launchers/preprocessors, each can have a global config, eg:

karma.configure({
  coffeePreprocessor: {
    options: {bare: false}
  }
});

What do you think ?

[iammerrick]

I would love to be able to use the latest configuration style to share common configuration. Any idea when a release is coming?

M

[abanctelchevrel]

Would love it too, especially for the ability to pass flag like --web-security=no to PhantomJS.

[vojtajina]

Sorry for delays, it's merged now. I hope to push a new release to npm this week.

[iammerrick]

Awesome anyway to get more tolerant fs integration in that release?

M

[vojtajina]

Sure thing, check out the comments I sent, I will wait for that PR. Thanks a bunch @iammerrick !

[hppycoder]

I was testing out the @canary release of this today and ran into an issue with the defineLauncher working with a custom flag.

karma.defineLauncher('my_chrome','Chrome', { flags: ['–-disable-web-security'] });

Version:
chadsmith@AC02K47M9FFT:~/www/mysite$ karma --version Karma version: 0.9.3

During the launch with LOG_DEBUG turned on:
DEBUG [launcher]: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --user-data-dir=/var/folders/mc/rsq_5h4962x68r0b25z6lk544001md/T/karma-22288871 --no-default-browser-check --no-first-run --disable-default-apps --start-maximized http://localhost:9877/__karmaRunner/?id=22288871

Did I do something wrong not to have --disable-web-security make it into the path?

[vojtajina]

@hppycoder Sorry, my bad. I didn't push chrome-launcher plugin to NPM. I'm getting all the plugins on automated tasks as Karma, so that I won't forget next time, hopefully ;-)

Can you please update karma-chrome-launcher to 0.0.2 ? It should work then...

[hppycoder]

@vojtajina - Perfect! Fixed the issue now and all seems to be working well. Thanks!

[hppycoder]

For all you fine Mac friends out there, you will need to set your launcher to look like this.

karma.defineLauncher('my_chrome','Chrome', {
      flags: ['--args –-disable-web-security']
  });

Notice that you have to first send in args, then follow it up with the disable-web-security. If not you will have a tab open in Chrome for nx --disable-web-security which isn't desired.

[vojtajina]

@hppycoder and others, I think you gonna hate me... but check out this #604 ;-)