mocha test runner & reporter for atom-coderoad
npm install mocha-coderoadAtom-CodeRoad Javascript test runner & reporter.
npm install mocha-coderoad
Use atom-snippets to quickly generate test files.
Open up Atom -> Open Your Snippets. Add the contents of mocha-coderoad snippets.cson to your global snippets.cson file.
Quickly generate tests using the following snippet prefixes:
* mochacr-f - test a function
* mochacr-a - test an array
* mochacr-o - test an object
It makes sense to write test statements using 'should', 'must' or negative statements. Remember, the failing test message will be delivered as feedback to the user.
``js`
it('should be a function')
it('must be a function')
it('isn\'t a function')
Use a loader to run the user saved file in the context of your file. Think of a loader as a way to place the file your testing inside of your test file. Loaders are written inside of comments.
`js`
// load('user-file.js');
/ workspaceDirectory/user-file.js /
When loading files within your tutorial directory, add a second parameter of true. This can allow you to low additional data variables or functions, for example: var data = {...}.
`js`
// load('data-file.js', true)
/ workspaceDirectory/node_modules/tutorial-name/tutorial/data-file.js /
Here are examples using mocha with chai's expect. See the docs.
#### exists
`js`
it('doesn\'t exist', function() {
expect(target).to.not.be.undefined;
});
#### type
`js`
it('should be a function', function() {
expect(target).to.be.a('function');
});
#### function params
`js`
it('should have two parameters', function() {
expect(target).to.have.length(2);
});
#### function returns
`js`
it('should add one to the number', function () {
expect(addOne(1)).to.equal(2);
});
#### equals
`js`
it('should be 42', function () {
expect(target).to.equal(42);
});
#### deep equals (with objects or arrays)
`js`
it('should be {a: 42}', function () {
expect(target).to.deep.equal({a: 42});
});
#### regex
`js`
it('should include the variable "count"', function () {
var regex = new RegExp('count');
var string = target.toString();
expect(string.match(regex)).to.be.true;
});
`js`
it('should access the property "prop"', function () {
var regex1 = /\.prop/; // dot notation
var regex2 = /\[["']prop["']\]/; // bracket notation
var string = target.toString();
var result = !!string.match(regex1) || !!string.match(regex2);
expect(result).to.be.true;
});
#### spies
You can use sinon or chai-spies to create a spy. See an example below:
> npm i -s chai-spies
`js
var chai = require('chai'),
spies = require('chai-spies');
var expect = chai.expect;
chai.use(spies);
var spy = chai.spy.on(console, 'log');
loadJS('04-forEach.js');
it('should write "hello world" to the console', function () {
expect(spy).to.have.been.called.with('hello world');
});
`
There are situations where you might want to change data based on the current task. In this case, be careful, as all earlier tests must continue to pass.
Some variables are passed into the test runner through the node environment process.env.
See an example of dynamic data based on the task position below:
`js
var data = [1, 2, 3];
if (process.env.TASK_POSITION === '4') {
data = [1, 2, 3, 4];
}
`
Tests can also change based on the task position.
`js`
if (process.env.TASK_POSITION !== '4') {
it('should do this', function () { ... });
} else {
it('should to that', function () { ... });
}
See a full example.
It's entirely possible to create a simplified testing tool that could make writing tests faster & easier.
The easiest solution would be to use editor snippets to generate a page of tests from a simple configuration object. This does not yet exist.
CodeRoad tutorial configurations can be set in the package.json config.
`json``
{
"config": {
"testDir": "tutorial",
"testSuffix": ".spec.js",
"testRunner": "mocha-coderoad",
"edit": true
}
}
This section will likely expand in the future. For now, let's go over some of the configurations.
#### testDir
The relative path to the unit test directory. This makes writing unit tests paths easier.
#### testSuffix
The common suffix for unit tests. Also making writing unit test paths shorter.
#### testRunner
Specified test runner. Currently only "mocha-coderoad" is available.
#### edit
If set to true, Atom-CodeRoad will allow users to submit issues or submit markdown pull requests. You will also need to specify "repository" & "bugs" in your package.json file. See an example config file.