Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Tiny test runner for Node.js
test()
function, plus .skip() and .only()Often for small projects, test suites consist of some wrapped assertions in test
or it
functions. Node.js has a fine
assert
module built-in, while exception output is prettier in Node v12. Last but not least, if any test fails, the
process should exit with a non-zero code so that CI/CD environments can act accordingly.
Turns out this isn't very hard to implement, bron is only <70 LOC. In case you need more from your test framework, I'm happy to recommend one of the more full fledged options:
Runner | Dependencies | Size |
---|---|---|
Bron (v1.0.0) | 0 | 3K |
Tape (v4.10.2) | 32 | 263K |
Mocha (v6.1.4) | 115 | 1.52M |
Ava (v2.0.0) | 453 | 3.95M |
beforeEach
, after
)npm install bron -D
Add a test
script to run the tests (npm test
), e.g.:
{
"scripts": {
"test": "bron test/*.js"
}
}
bron <file> [--serial]
const test = require('bron');
const assert = require('assert').strict;
const add = (x, y) => x + y;
test('should pass', () => {
assert.equal(add(1, 2), 3);
});
test('should fail', () => {
assert.equal(add(1, 2), 4);
});
$ bron test.js
✔ should pass
✖ should fail
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
3 !== 4
at /Users/lars/Projects/bron/sync.js:11:10
...
✖ 1 test(s) failed
✔ 1 test(s) passed
No magic, but know that the tests run in parallel.
const addAsync = (x, y) => (x && y ? Promise.resolve(x + y) : Promise.reject('no can do'));
test('should pass with resolved promise', () => {
assert.doesNotReject(addAsync(1, 2));
});
test('should pass with rejected promise', () => {
assert.rejects(addAsync(1), /no can do/);
});
Add --serial
:
const wait = ms => new Promise(r => setTimeout(r, ms));
test('should run serial (first)', async () => {
await wait(100);
assert(true);
});
test('should run serial (last)', async () => {
await wait(0);
assert(true);
});
$ bron --serial
✔ should run serial (first)
✔ should run serial (last)
Return a promise, and the test will pass (resolved) or fail (rejected).
const addAsync = (x, y) => (x && y ? Promise.resolve(x + y) : Promise.reject('no can do'));
test('should pass with resolved promise', () => {
return addAsync(1, 2);
});
test('should fail with rejected promise', () => {
return addAsync(1);
});
$ bron
✔ should pass with resolved promise
✖ should fail with rejected promise
no can do
✖ 1 test(s) failed.
✔ 1 test(s) passed.
test.skip('should be skipped', () => {
assert.equal(1, 1);
});
test.only('should pass', () => {
assert.equal(1, 1);
});
test('should be skipped', () => {
assert.equal(1, 1);
});
You can use .only
multiple times (each .only
will run).
FAQs
Tiny test runner
The npm package bron receives a total of 7 weekly downloads. As such, bron popularity was classified as not popular.
We found that bron 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
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.