4.2.3 • Published 3 years ago

@sealsystems/mocha v4.2.3

Weekly downloads
51
License
MIT
Repository
github
Last release
3 years ago

@sealsystems/mocha

Mocha executable and test configuration for SEAL Systems

Installation

npm install --save-dev @sealsystems/mocha

Quick start

Mocha is installed as a dependency of @sealsystems/mocha. So you can call mocha from the root directory of your project:

$(npm bin)/mocha

The package also provides some CLI executables:

  • test-run runs Mocha

  • test-coverage collects coverage data via nyc (which is also installed as a dependency)

  • test-coverage-check collects coverage data and fails if threshold (80% for all criteria) has not been reached

  • test-report collect coverage data and opens the generated HTML page

Please note:

  • Our standard assert library assertthat is also a dependency of this package. So you do not need to include it in your project's package.json.

  • In order to install all dependencies directly in the project's node_modules folder, you may need to delete package-lock.json before adding this package.

  • Mocha runs with the following settings:

    test/**/*Test.js
    --async-only
    --bail
    --color
    --exit
    --recursive
    --ui tdd

To use these executables, add some scripts to your package.json:

...
"scripts": {
  "test": "test-run",
  "test:coverage": "test-coverage",
  "test:coverage:check": "test-coverage-check",
  "test:report": "test-report"
}
...

And call them via npm run:

npm run test
npm run test:coverage
npm run test:coverage:check
npm run test:report

Command line parameter

The commands evaluate command line parameters from package.json. All parameters prefixed with -mocha are passed to mocha without the prefix. All parameters prefixed with -ny are passed to nyc without the prefix.

Example:

"scripts": {
  "test": "test-run -mocha--max-old-space-size=2500 -nyc--check-coverage"
}

The above example runs mocha with the extra parameter --max-old-space-size=2500 and nyc with the extra parameter --check-coverage.

Implementation details

Please note: This module is part of the build and release infrastructure. In order to prevent endless loops when automatically updating dependencies, Dependabot is not enabled.

4.2.3

3 years ago

4.2.2

3 years ago

4.2.1

3 years ago

4.2.0

4 years ago

4.1.11

4 years ago

4.1.10

4 years ago

4.1.9

4 years ago

4.1.8

4 years ago

4.1.7

5 years ago

4.1.6

5 years ago

4.1.5

5 years ago

4.1.4

5 years ago

4.1.3

5 years ago

4.1.2

5 years ago

4.1.1

6 years ago

4.1.0

6 years ago

4.0.0

6 years ago

3.0.15

6 years ago

3.0.14

6 years ago

3.0.13

6 years ago

3.0.12

6 years ago

3.0.11

6 years ago

3.0.10

6 years ago

3.0.9

6 years ago

3.0.8

6 years ago

3.0.7

6 years ago

3.0.6

6 years ago

3.0.5

6 years ago

3.0.4

6 years ago

3.0.3

6 years ago

3.0.2

6 years ago

3.0.1

6 years ago

3.0.0

6 years ago

2.1.0

6 years ago

2.0.3

6 years ago

2.0.2

6 years ago

2.0.1

6 years ago

2.0.0

6 years ago