-
Notifications
You must be signed in to change notification settings - Fork 659
Closed
Description
I noticed that the final config of karma is generated in gulp and there is no easy way getting it without the changing the gulp files (as far as I know). I was thinking that there should be a way to kind of keep everything in a karma config.
For example there is other yo generator (https://github.com/johnpapa/generator-hottowel) for angular from creator who maintains the famous angular style guide (https://github.com/johnpapa/angular-styleguide). The generator tries to follow angular style guide he wrote:
This is how his generated karma config looks:
module.exports = function(config) {
var gulpConfig = require('./gulp.config')();
config.set({
// base path that will be used to resolve all patterns (eg. files, exclude)
basePath: './',
// frameworks to use
// some available frameworks: https://npmjs.org/browse/keyword/karma-adapter
frameworks: ['mocha', 'chai', 'sinon', 'chai-sinon'],
// list of files / patterns to load in the browser
files: gulpConfig.karma.files,
// list of files to exclude
exclude: gulpConfig.karma.exclude,
proxies: {
'/': 'http://localhost:8888/'
},
// preprocess matching files before serving them to the browser
// available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
preprocessors: gulpConfig.karma.preprocessors,
// test results reporter to use
// possible values: 'dots', 'progress', 'coverage'
// available reporters: https://npmjs.org/browse/keyword/karma-reporter
reporters: ['progress', 'coverage'],
coverageReporter: {
dir: gulpConfig.karma.coverage.dir,
reporters: gulpConfig.karma.coverage.reporters
},
// web server port
port: 9876,
// enable / disable colors in the output (reporters and logs)
colors: true,
// level of logging
// possible values: config.LOG_DISABLE || config.LOG_ERROR ||
// config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
logLevel: config.LOG_INFO,
// enable / disable watching file and executing tests whenever any file changes
autoWatch: true,
// start these browsers
// available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
// browsers: ['Chrome', 'ChromeCanary', 'FirefoxAurora', 'Safari', 'PhantomJS'],
browsers: ['PhantomJS'],
// Continuous Integration mode
// if true, Karma captures browsers, runs the tests and exits
singleRun: false
});
};
So by doing this way it might be more flexible and it should work with WebStorm karma runner. Or maybe someone know how to start WebStorm with current karma setup ?
Metadata
Metadata
Assignees
Labels
No labels