Package Exports
- ddt-js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (ddt-js) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
ddt.js
Simple but powerful data-driven unit testing utility
Features
- Optimized for testing synchronous functions
- Tests are defined in JSON-like code, alongside main code, enabling great flexibility
Installation
npm install -g --save ddt-js
Module Usage
var ddt = require('ddt-js);
let sayHello = function(person){
if (!person && person !== false)
throw "invalid person";
else
return "Hello " + person;
}
ddt.test({
title: "test sayHello() with actual person",
unit: sayHello,
getArgs: function() { return ["World"]; },
getExpected: function() { return "Hello World"; }
})output:
{
title: "test sayHello with actual person",
unit: sayHello,
args: ["World"],
expected: "Hello World",
actual: "Hello World",
passed: true
}Command-Line Usage
ddt --src foo/bar/*.js --dest foo/bar --ext .test.result --test-info-key testInfo
The command line options are:
- src: source files glob
- dest: destination folder for test results; if omitted, result files are saved in the same folder as each source file
- ext: extension for test result files
- test-info-key: specifies the property of each source module that contains the test information.
The ddt command-line assumes each file in the source glob defines a single module together with its test information. To be testable, the module definition must export a test information object (by default named "testInfo") that specifies the folowing members:
- cases: An array of test cases
- getContext(): a function that returns a global context object for all the test cases in the module
- defaultUnit: the default function to be tested. Each test case in the module can specify its own unit to override this value, but in situations where most of the test cases are testing the same unit, that unit can be specified here
Example module for command-line ddt testing:
module.exports.sayHello = function(person){
if (!person && person !== false)
throw "invalid person";
else
return "Hello " + person;
}
module.exports.testInfo = {
defaultUnit: sayHello,
getContext: function() { return null; },
cases: [
{
title: "sayHello() return correct output with actual person",
// unit: sayHello,
getArgs: function() { return ["World"]; },
getExpected: function() { return "Hello World"; }
},
{
title: "sayHello() return correct error with null person",
// unit: sayHello,
getArgs: function() { return [null]; },
getExpected: function() { return "invalid person"; }
}
]
})