Security News
The Unpaid Backbone of Open Source: Solo Maintainers Face Increasing Security Demands
Solo open source maintainers face burnout and security challenges, with 60% unpaid and 60% considering quitting.
npm install mocha-tags --save-dev
tags('network')
.describe(/* ... */)
tags('integration', 'fast')
.it(/* ... */)
By default all tests will run as usual,
but you can use the --tags
option to filter them:
mocha --tags "is:integration not:slow not:network"
Tests that don't match the criteria are skipped with the xdescribe
or xit
commands,
and appear as pending
in the test output.
Note: because of the way filtering works, tags have to be a single word, without any spaces.
is:<tag>
Run tests with the X
tag
mocha --tags "is:X"
Run tests with the X
or Y
tags
mocha --tags "is:X is:Y"
Run tests with the X
and Y
tag
mocha --tags "is:X+Y"
not:<tag>
Don't run tests with the X flag
mocha --tags "not:X"
Don't run tests with the X or Y flag
mocha --tags "not:X not:Y"
Don't run tests with the X and Y flag
mocha --tags "not:X+Y"
You might want to exclude certain tags based on complex logic.
This is not easy to define from the command line, so mocha-tags
exposes its filter programmatically.
var tags = require('mocha-tags');
// either replace the entire filter
tags.filter = new tags.Filter('not:trading-hours');
// or simply modify the existing one
if (moment().hours() < 8 || moment().hours() > 18) {
tags.filter.remove('not:unit');
tags.filter.add('not:trading-hours');
}
tags('trading-hours').it(
// some integration test than can only run during core hours
);
Skipped tests appear as pending
in the test output,
so you should always notice any test that was skipped by accident.
It also helps to add the following at the top of your main test file / spec helper.
var tags = require('mocha-tags');
console.log('Test filter: ', tags.filter);
mocha-tags
supports the following keywords:
tags().describe
: normal usagetags().describe.only
: ignores any tags and filters, and runs by itselftags().xdescribe
: ignored regardless of tags...and the same pattern for it
.
You can also add custom test hooks by setting the following property:
tags.hooks = function(either) {
this.mytest = either(fnMatch, fnSkip);
};
// to be used as
tags('hello', 'world').mytest(/* arguments */);
// which will call either
fnMatch(/* arguments */);
fnSkip(/* arguments */);
FAQs
Add tags to your mocha test suite, and filter them at runtime
We found that mocha-tags demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Solo open source maintainers face burnout and security challenges, with 60% unpaid and 60% considering quitting.
Security News
License exceptions modify the terms of open source licenses, impacting how software can be used, modified, and distributed. Developers should be aware of the legal implications of these exceptions.
Security News
A developer is accusing Tencent of violating the GPL by modifying a Python utility and changing its license to BSD, highlighting the importance of copyleft compliance.