mocha-multi-reporters

Generate multiple mocha reports in a single mocha execution.

!npm version
!npm

Install

``
npm install mocha-multi-reporters --save-dev
`

Demo

`bash
$ ./node_modules/.bin/mocha --reporter mocha-multi-reporters
mocha-test #1
✓ sample test #1.1
✓ sample test #1.2

mocha-test #2
✓ sample test #2.1
- sample test #2.2


3 passing (6ms)
1 pending







`

$3

Set the reporters configuration using --reporter-options configFile=config.json.
- Include reporters in reporterEnabled as a comma-delimited list
`js
{
"reporterEnabled": "spec, @my-org/custom"
}
`
- Specify each reporter's configuration using its camel-cased name, followed by reporterOptions, as key.
> For scoped reporters such as example @myorg/custom, remove all special characters.
`js
{
"reporterEnabled": "spec, @my-org/custom",
"myOrgCustomReporterOptions": {
// [...]
}
}
`

#### Examples:

* Generate spec and json reports.

`js
// File: config.json
{
"reporterEnabled": "spec, json"
}
`

`bash
$ ./node_modules/.bin/mocha --reporter mocha-multi-reporters --reporter-options configFile=config.json
mocha-test #1
✓ sample test #1.1
✓ sample test #1.2

mocha-test #2
✓ sample test #2.1
- sample test #2.2


3 passing (6ms)
1 pending

{
"stats": {
"suites": 2,
"tests": 4,
"passes": 3,
"pending": 1,
"failures": 0,
"start": "2015-12-30T22:49:39.713Z",
"end": "2015-12-30T22:49:39.717Z",
"duration": 4
},
"tests": [
{
"title": "sample test #1.1",
"fullTitle": "mocha-test #1 sample test #1.1",
"duration": 1,
"err": {}
},
{
"title": "sample test #1.2",
"fullTitle": "mocha-test #1 sample test #1.2",
"duration": 0,
"err": {}
},
{
"title": "sample test #2.1",
"fullTitle": "mocha-test #2 sample test #2.1",
"duration": 0,
"err": {}
},
{
"title": "sample test #2.2",
"fullTitle": "mocha-test #2 sample test #2.2",
"err": {}
}
],
"pending": [
{
"title": "sample test #2.2",
"fullTitle": "mocha-test #2 sample test #2.2",
"err": {}
}
],
"failures": [],
"passes": [
{
"title": "sample test #1.1",
"fullTitle": "mocha-test #1 sample test #1.1",
"duration": 1,
"err": {}
},
{
"title": "sample test #1.2",
"fullTitle": "mocha-test #1 sample test #1.2",
"duration": 0,
"err": {}
},
{
"title": "sample test #2.1",
"fullTitle": "mocha-test #2 sample test #2.1",
"duration": 0,
"err": {}
}
]
}%
`

* Generate tap and xunit reports.

`js
// File: config.json
{
"reporterEnabled": "tap, xunit",
"xunitReporterOptions": {
"output": "xunit-custom.xml"
}
}
`
`bash
$ ./node_modules/.bin/mocha --reporter mocha-multi-reporters --reporter-options configFile=config.json

1..4
ok 1 mocha-test 1 sample test 1.1
ok 2 mocha-test 1 sample test 1.2
ok 3 mocha-test 2 sample test 2.1
ok 4 mocha-test 2 sample test 2.2 # SKIP -


tests 3

$ cat xunit-custom.xml






`

* Generate tap and junit reports.

To generate junit report, we are using mocha-junit-reporter.

`bash
$ npm install mocha-junit-reporter
`
`js
// File: config.json
{
"reporterEnabled": "mocha-junit-reporter",
"mochaJunitReporterReporterOptions": {
"mochaFile": "junit-custom.xml"
}
}
`
`bash
$ ./node_modules/.bin/mocha --reporter mocha-multi-reporters --reporter-options configFile=config.json

1..4
ok 1 mocha-test 1 sample test 1.1
ok 2 mocha-test 1 sample test 1.2
ok 3 mocha-test 2 sample test 2.1
ok 4 mocha-test 2 sample test 2.2 # SKIP -


tests 3

$ cat xunit-custom.xml















`

$3

This option lets you dynamically replace the output files of reporter options.

In your Mocha --reporterOptions, specify cmrOutput with a plug-sign-separated
list of the reporter name, the property on that reporter's options to have replaced, and the dynamic ID you would like substituted. If you need multiple reporters
to have dynamic output, add additional plus-sign-separated lists separated by colons.

`sh
mocha --reporter mocha-multi-reporters --reporterOptions configFile=mocha-multi-reporters.json,cmrOutput=@mochajs/json-file-reporter+output+specialID tests
`

`js
// mocha-multi-reporters.json
{
"mochajsJsonFileReporterReporterOptions": {
"output": "tests/results/file-{id}.json"
},
"reporterEnabled": "spec, @mochajs/json-file-reporter"
}
`

This will produce an output for @mochajs/json-file-reporter
reporterOptions with the value:

> tests/results/file-specialID.json

$3

Note that when Mocha is called programmatically, it is passed an options object when created. This object is usually derived from a config file that your mocha test runner reads prior to instantiation. This is the object that must contain a key reporter with a value of mocha-multi-reporters for this plugin to be used. You can also pass the key reporterOptions with a value of any of the above listed config files (including the reporterEnabled subkey and any other plugin configuration information.) This removes the requirement to have an intermediate configuration file specifically for the multireporter configuration.

`js
const mocha = new Mocha({
reporter: "mocha-multi-reporters",
timeout: config.testTimeout || 60000,
slow: config.slow || 10000,
reporterOptions: {
"reporterEnabled": "mocha-junit-reporter, tap",
"mochaJunitReporterReporterOptions": {
"mochaFile": "junit-custom.xml"
}
}
});
mocha.addFile(...)
mocha.run(...)

`
Note that it will first check if reporterOptions contains a configFile key, and if it does, use that. That key must not exist in the reporterOptions` object in order to pass these values in directly.

License

The MIT License (MIT)

Copyright(c) 2019 Yousaf Nabi
Copyright(c) 2017 Stanley Ng

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.