npm i -D karma-webpack
// Karma configuration
module.exports = function(config) {
config.set({
// ... normal karma configuration
files: [
// all files ending in "_test"
{pattern: 'test/*_test.js', watched: false},
{pattern: 'test/**/*_test.js', watched: false}
// each file acts as entry point for the webpack configuration
],
preprocessors: {
// add webpack as preprocessor
'test/*_test.js': ['webpack'],
'test/**/*_test.js': ['webpack']
},
webpack: {
// karma watches the test entry points
// (you don't need to specify the entry option)
// webpack watches dependencies
// webpack configuration
},
webpackMiddleware: {
// webpack-dev-middleware configuration
// i. e.
stats: 'errors-only'
}
});
};
This configuration is more performant, but you cannot run single test anymore (only the complete suite).
The above configuration generates a webpack bundle for each test. For many testcases this can result in many big files. The alternative configuration creates a single bundle with all testcases.
files: [
// only specify one entry point
// and require all tests in there
'test/test_index.js'
],
preprocessors: {
// add webpack as preprocessor
'test/test_index.js': ['webpack']
},
// test/test_index.js
// require all modules ending in "_test" from the
// current directory and all subdirectories
var testsContext = require.context(".", true, /_test$/);
testsContext.keys().forEach(function(path) {
try {
testsContext(path);
} catch(err) {
console.error('[ERROR] WITH SPEC FILE: ', path);
console.error(err);
}
});
Every test file is required using the require.context and compiled with webpack into one test bundle.
- In your
karma.conf.js
get the params from the terminal:
var files = (process.env.npm_config_single_file) ? process.env.npm_config_single_file : 'test/test_index.js';
Don't forget that we still want to support the normal test/test_index.js
process that run all the tests (see "Alternative Usage").
- In order to run a single test you will need to set an option object with all your configuration (Without files and preprocessors):
var option = {
webpack: {
// webpack configuration
},
// more configuration......
};
- Set your files path and preprocessors:
option.files = [
{pattern: files, watch: false}
];
option.preprocessors = {};
option.preprocessors[files] = [ 'webpack', 'sourcemap' ];
// call config.set function
config.set(option);
- Run in the terminal:
npm test --single_file=**/my-specific-file-spec.js
You can use the karma-sourcemap-loader
to get the source maps generated for your test bundle.
npm install --save-dev karma-sourcemap-loader
And then add it to your preprocessors
preprocessors: {
'test/test_index.js': ['webpack', 'sourcemap']
}
And tell webpack to generate sourcemaps
webpack: {
// ...
devtool: 'inline-source-map'
}
This is the full list of options you can specify in your Karma config.
Webpack configuration.
Configuration for webpack-dev-middleware.
beforeMiddleware
is a webpack option that allows injecting middleware before
karama's own middleware are run. This loader provides a webpackBlocker
middleware that will block tests from running until code recompiles. That is,
given this scenario:
- Have a browser open on the karma debug page (http://localhost:9876/debug.html)
- Make a code change
- Refresh
Without the webpackBlocker
middleware karma will serve files from before
the code change. With the webpackBlocker
middleware the loader will not serve
the files until the code has finished recompiling.
Note that the beforeMiddleware
option is only supported in karma with version >1.0.
Karma Webpack does not support the CommonChunksPlugin
, the ExtractTextPlugin
, or the DllPlugin
.
Mika Kalathil |
Joshua Wiens |
Will Farley |
Daniela Valero |
The MIT License (MIT)
Copyright (c) 2014 - 2016 Tobias Koppers
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.