Skip to content

Latest commit

 

History

History
117 lines (74 loc) · 4.84 KB

README.md

File metadata and controls

117 lines (74 loc) · 4.84 KB

TS-Mocha

Latest Stable Version NPM Downloads NPM Downloads Codeship Status for piotrwitek/ts-mocha Greenkeeper badge

ts-mocha is a wrapper on top of mocha to allow running tests written in TypeScript without setting up a complicated setup in your project, it just works.

All mocha features are available without any limitation because ts-mocha is passing all the params to original mocha behind the scenes.

Why?

To setup Mocha with TypeScript you need to figure out how to set it up together, it's not an easy task and require some time and effort to setup correctly. Moreover this setup will stop working whenever mocha or ts-node introduce breaking changes, so you'll have to fix it and waste your time again.

This package handles all that concerns for you and let you use ts-mocha in the same way as a regular mocha while supporting TypeScript.

Also we added some useful options to make your life easier specifically for TypeScript projects, you can find them below.

How?

TS-Mocha has one only dependency - ts-node, which is used as a TypeScript runtime to execute tests that can import and run imported TypeScript source files as well. It is a thin wrapper that run node process with mocha and set up ts-node environment to handle .ts and .tsx files. To speed up TypeScript tests execution type-checking is disabled, using only transpile mode.

NOTE: This package does not include Mocha - Mocha is set as peer dependency, so I don't lock the consumer to a specific Mocha version and I don't have to update this package when Mocha is updated.

PRO TIP: To make your developer experience better I recommend to run type-checking in a separate process by starting TSC compiler (preferably in watch mode) in you terminal with --noEmit and --project flags.

Installation

# remember to install mocha if you don't have it already (npm i -D mocha)

npm i -D ts-mocha

# install recent Mocha and Expect @types packages for best DX
npm i -D @types/mocha @types/expect

Usage

- CLI Usage

CLI options consist of all the options of regular Mocha plus extra options below:

-p, --project <value> - relative or absolute path to a tsconfig.json file (equivalent of tsc -p <value>) [default: "./tsconfig.json"]

Example:

ts-mocha -p src/tsconfig.json src/**/*.spec.ts

--paths - feature toggle flag to enable tsconfig-paths integration [default: false]

tsconfig-paths is an optional dependency, make sure to install it locally in your project

When using path mapping via the paths compiler option in tsconfig.json this library utilizes the tsconfig-paths package, allowing for automatic resolution of aliased modules locations during test execution.

Check our test suite for a reference implementation: Link

Example:

ts-mocha --paths -p src/ src/**/*.spec.ts

--type-check - feature toggle flag to enable type checking in ts-node [default: false]

By default ts-mocha uses the --transpile-only option of ts-node to make tests run faster. Use the --type-check option to enable type checking in ts-node.

Example:

ts-mocha --type-check -p src/ src/**/*.spec.ts

Watch Mode

If you want your tests to be automatically rerun when your code changes, add both the -w flag and the --watch-files flag telling it to watch for typescript files.

Example:

ts-mocha test/**/*.spec.ts -w --watch-files '**/*.ts'

- Programmatic usage

In code you can use ts-mocha by adding a single require at the beginning of your script:

// set env variable to the `tsconfig.json` path before loading mocha (default: './tsconfig.json')
process.env.TS_NODE_PROJECT = './src/tsconfig.json'

// Optional: set env variable to enable `tsconfig-paths` integration
process.env.TS_CONFIG_PATHS = true;

// register mocha wrapper
require('ts-mocha');

For example:

process.env.TS_NODE_PROJECT = './src/tsconfig.json';
require('ts-mocha');
const Mocha = require('mocha');

const mocha = new Mocha();
mocha.addFile(`./src/file.spec.ts`);
mocha.run((failures) => {
  process.on('exit', () => {
    process.exit(failures); // exit with non-zero status if there were failures
  });
});