Skip to content

Commit

Permalink
test: add test-benchmark-crypto
Browse files Browse the repository at this point in the history
Add minimal test for crypto benchmarks. It makes sure that they can run
without returning an error code.

PR-URL: #12347
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
  • Loading branch information
Trott authored and evanlucas committed May 1, 2017
1 parent 354df94 commit 81615f2
Showing 1 changed file with 36 additions and 0 deletions.
36 changes: 36 additions & 0 deletions test/parallel/test-benchmark-crypto.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
'use strict';

const common = require('../common');

if (!common.hasCrypto) {
common.skip('missing crypto');
return;
}

if (common.hasFipsCrypto) {
common.skip('some benchmarks are FIPS-incompatible');
return;
}

// Minimal test for crypto benchmarks. This makes sure the benchmarks aren't
// horribly broken but nothing more than that.

const assert = require('assert');
const fork = require('child_process').fork;
const path = require('path');

const runjs = path.join(__dirname, '..', '..', 'benchmark', 'run.js');
const argv = ['--set', 'n=1',
'--set', 'writes=1',
'--set', 'len=1',
'--set', 'api=stream',
'--set', 'out=buffer',
'--set', 'keylen=1024',
'--set', 'type=buf',
'crypto'];

const child = fork(runjs, argv, {env: {NODEJS_BENCHMARK_ZERO_ALLOWED: 1}});
child.on('exit', (code, signal) => {
assert.strictEqual(code, 0);
assert.strictEqual(signal, null);
});

0 comments on commit 81615f2

Please sign in to comment.