json-reporter
Advanced tools
Comparing version 0.0.1 to 0.1.0
# Change Log | ||
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines. | ||
<a name="0.1.0"></a> | ||
# 0.1.0 (2017-03-01) | ||
### Bug Fixes | ||
* improve readme ([84272ce](https://github.com/gemini-testing/json-reporter/commit/84272ce)) | ||
### Features | ||
* implement core functionality ([65fc627](https://github.com/gemini-testing/json-reporter/commit/65fc627)) | ||
# Change Log | ||
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines. |
{ | ||
"name": "json-reporter", | ||
"version": "0.0.1", | ||
"version": "0.1.0", | ||
"description": "Common plugin for gemini and hermione which is intended to aggregate the results of tests running", | ||
@@ -38,2 +38,3 @@ "main": "gemini.js", | ||
"fs-extra": "^2.0.0", | ||
"gemini-configparser": "^0.3.0", | ||
"lodash": "^4.17.4" | ||
@@ -49,2 +50,3 @@ }, | ||
"mocha": "^3.0.2", | ||
"proxyquire": "^1.7.11", | ||
"sinon": "^1.17.5", | ||
@@ -51,0 +53,0 @@ "standard-version": "^4.0.0" |
# json-reporter | ||
[![npm](https://img.shields.io/npm/v/json-reporter.svg?maxAge=2592000)](https://www.npmjs.com/package/json-reporter) | ||
[![npm](https://img.shields.io/npm/v/json-reporter.svg)](https://www.npmjs.com/package/json-reporter) | ||
[![Build Status](https://travis-ci.org/gemini-testing/json-reporter.svg?branch=master)](https://travis-ci.org/gemini-testing/json-reporter) | ||
@@ -22,1 +22,62 @@ [![Coverage Status](https://img.shields.io/coveralls/gemini-testing/json-reporter.svg?style=flat)](https://coveralls.io/r/gemini-testing/json-reporter?branch=master) | ||
``` | ||
## Usage | ||
Plugin has following configuration: | ||
* **enabled** (optional) `Boolean` – enable/disable the plugin; by default plugin is enabled | ||
* **path** (optional) `String` - path for saving json report file; by default json report will be saved into `json-reporter.json` inside current work directory. | ||
Also there is ability to override plugin parameters by CLI options or environment variables | ||
(see [configparser](https://github.com/gemini-testing/configparser)). | ||
### Gemini usage | ||
Add plugin to your `gemini` config file: | ||
```js | ||
module.exports = { | ||
// ... | ||
plugins: { | ||
'json-reporter/gemini': { | ||
enabled: true, | ||
path: 'my/custom/report.json' | ||
} | ||
}, | ||
//... | ||
} | ||
``` | ||
### Hermione usage | ||
Add plugin to your `hermione` config file: | ||
```js | ||
module.exports = { | ||
// ... | ||
plugins: { | ||
'json-reporter/hermione': { | ||
enabled: true, | ||
path: 'my/custom/report.json' | ||
} | ||
}, | ||
//... | ||
} | ||
``` | ||
## Testing | ||
Run [mocha](http://mochajs.org) tests: | ||
```bash | ||
npm run test-unit | ||
``` | ||
Run tests with [istanbul](https://github.com/gotwarlost/istanbul) coverage calculation: | ||
```bash | ||
npm run cover | ||
``` | ||
Run [eslint](http://eslint.org) codestyle verification | ||
```bash | ||
npm run lint | ||
``` |
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 1 instance in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Empty package
Supply chain riskPackage does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.
Found 1 instance in 1 package
29199
16
178
83
0
4
10
2
+ Addedgemini-configparser@^0.3.0
+ Addedbabel-runtime@5.8.38(transitive)
+ Addedcore-js@1.2.7(transitive)
+ Addedgemini-configparser@0.3.0(transitive)
+ Addedlodash@3.10.1(transitive)