NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #4946 most downloaded on npm
Spectacular Test Runner for JavaScript.
Latest stable
6.4.4
Last release 2 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 10 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
14 years old
213 releases · first in 2013
Drag across the ruler to compare, or tap a release to open it.
launcher kill method which was throwing an error if no callback was specified
<a name="v0.11.0"></a>
<a name="v0.10.2"></a>
Your coding agent can read these notes before it upgrades. Set up the MCP server →
reporter: print browser stats immediately after it finishes
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
don't mark a browser captured if already being killed/timeouted (2123097), closes #88
cli: Always pass an instance of fs to processArgs. (06532b7), closes #677
Nothing published for this version
runner: do not confuse client args with the config file
<a name="v0.9.7"></a>
init: install plugin as dev dependency
<a name="v0.9.6"></a>
pass command line opts through to browser
runnerPort is merged with port
if you are using karma run with custom --runer-port, please change that to --port.
(ca4c4d88)<a name="v0.9.5"></a>
init: generate config with the new syntax
<a name="v0.9.4"></a>
config: allow parsing the config multiple times
// before:
module.exports = function(karma) {
karma.configure({port: 123});
karma.defineLauncher('x', 'Chrome', {
flags: ['--disable-web-security']
});
karma.definePreprocessor('y', 'coffee', {
bare: false
});
karma.defineReporter('z', 'coverage', {
type: 'html'
});
};
// after:
module.exports = function(config) {
config.set({
port: 123,
customLaunchers: {
'x': {
base: 'Chrome',
flags: ['--disable-web-security']
}
},
customPreprocessors: {
'y': {
base: 'coffee',
bare: false
}
},
customReporters: {
'z': {
base: 'coverage',
type: 'html'
}
}
});
};
<a name="v0.9.3"></a>
capturing console.log on IE (fa4b686a, closes #329)
karma-* (405a5a62)console.* log methods (683e6dcb)module.exports = function(karma) {
karma.configure({
autoWatch: true,
// ...
});
};
<a name="v0.9.2"></a>
better error reporting when loading plugins
Nothing published for this version
init: to not give false warning about missing requirejs
<a name="v0.9.0"></a>
reporters, launchers, preprocessors, adapters are separate plugins now, in order to use them, you need to install the npm package (probably add it as a devDependency into your package.json) and load in the karma.conf.js with plugins = ['karma-jasmine', ...]. Karma ships with couple of default plugins (karma-jasmine, karma-chrome-launcher, karma-phantomjs-launcher).
frameworks (such as jasmine, mocha, qunit) are configured using frameworks = ['jasmine']; instead of prepending JASMINE_ADAPTER into files.
<a name="v0.8.0"></a>
testacular start becomes karma start.karma.conf.js.__testacular__ object in the client code, change it to __karma__, eg. window.__testacular__.files becomes window.__karma__.files. (026a20f7)<a name="v0.6.1"></a>
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.