My experience of using the grunt-karma plugin was such that I spend more time debugging the plugin than on my actual site. My solution is to exclude it completely and use grunt-exec to run my karma command or just not use grunt and start karma manually in a new tab.
grunt.loadNpmTasks('grunt-exec'); var config = { exec: { karma : 'karma start {path to your karma.conf.js file}'
I know that this is probably not the answer you are looking for, but my experience has led me to realize that every step you get from the original program is just an extra program that you have to debug, which is not yours own.
WHAT, being said, your files do not seem to be included.
I usually split the karma configuration file into separate files:
config /files.js
module.exports = [ 'public/lib/angular/angular.js', 'public/lib/lodash/dist/lodash.compat.js', 'public/lib/jquery/dist/jquery.js', 'public/lib/angular-ui-router/release/angular-ui-router.js', 'tests/test-main.js', {pattern: 'public/js/**/*.js', included: true}, {pattern: 'tests/unit/**/*.js', included: true} ];
config /common.conf.js
var files = require('./files.js'); module.exports = { // base path that will be used to resolve all patterns (eg. files, exclude) basePath: '../', frameworks: ['jasmine', 'requirejs'], // list of files / patterns to load in the browser files: files, // list of files to exclude exclude: [ ], // web server port port: 9876, // enable / disable colors in the output (reporters and logs) colors: true, // enable / disable watching file and executing tests whenever any file changes autoWatch: true, coverageReporter: { type : 'html', dir : './tests/coverage/', subdir: function(browser) { "use strict"; // normalization process to keep a consistent browser name accross different // OS return browser.toLowerCase().split(/[ /-]/)[0]; } }, };
config /karma.conf.js
var commonConfig = require ('./common.conf.js');
module.exports = function(config) { "use strict"; commonConfig.reporters = ['nyan', 'growl']; commonConfig.browsers = ['PhantomJS']; commonConfig.captureTimeout = 60000; commonConfig.singleRun = false; commonConfig.logLevel = config.LOG_DEBUG; config.set(commonConfig); }; // commonConfig.browsers = ['PhantomJS', 'Chrome'] // commonConfig.browsers = ['PhantomJS', 'Chrome', 'Safari', 'Firefox'],
config /build.conf.js
var commonConfig = require('./common.conf.js'); module.exports = function(config) { "use strict"; commonConfig.reporters = ['progress']; commonConfig.browsers = ['PhantomJS']; commonConfig.captureTimeout = 120000; commonConfig.singleRun = true; commonConfig.logLevel = config.LOG_DEBUG; config.set(commonConfig); };
config /test.coverage.js
var commonConfig = require('./common.conf.js'); module.exports = function(config) { "use strict"; commonConfig.reporters = ['progress','coverage']; commonConfig.browsers = ['PhantomJS', 'Chrome', 'Safari', 'Firefox']; commonConfig.captureTimeout = 120000; commonConfig.singleRun = true; commonConfig.logLevel = config.LOG_DEBUG; commonConfig.preprocessors = {}; commonConfig.preprocessors['./public/js/*.js'] = ['coverage']; config.set(commonConfig); };
which allows me to run different karma configurations for different situations.
In development, I use: karma start config / karma.conf.js
To get my test coverage in all browsers, I would run: karma start config / test.coverage.js
and make sure my builds are clean as part of my ongoing integration process that I run karma start config / build.conf.js
Using this method, I can again use grunt-exec to run these commands at appropriate times.