@snaptopixel/testify

Easily test browser-ish Typescript projects with mocha

Downloads in past

Stats

StarsIssuesVersionUpdatedCreatedSize
@snaptopixel/testify
0160.5.85 years ago6 years agoMinified + gzip package size for @snaptopixel/testify in KB

Readme

testify
An opinionated configuration and tool for testing browser-based Typescript projects with Mocha.
šŸ’” Builds upon many of the ideas from @tomazzaman's excellent article ā€œHow to get fast unit tests with(out) Webpackā€

What it does

Initializes and configures a testing environment with the following:
  • ts-node for writing tests and transpiling .ts imports
  • mocha for running tests
  • sinon for mocking/stubbing functions
  • chai for assertions w/
- sinon-chai - chai-dom
  • jsdom for a browser-esque environment

āœØ Bonus features

  • šŸ˜ No webpack
  • šŸš€ Tracks test files and dependencies in watch mode and re-runs tests

Using it in your projects

Install with yarn or npm

yarn add @snaptopixel/testify

Configure with cosmiconfig

Testify can be configured via:
  • testify object in package.json
  • .testifyrc file in yaml or json format
  • testify.config.js file

Supported properties:
  • files - minimatch glob pattern for test files, ie: src/**/*.spec.ts
  • src - minimatch glob pattern for source files, ie: src/**/*.ts
  • require - array of file paths to include, useful for customizing the test environment
  • alias - map of path/file aliases for requiring files,ie: "@": "src"

Add run script(s) to package.json

"test": "testify"

Watch mode

Pass -w to run tests in watch mode
npm run test -- -w
Or add it as a package.json script
"test.watch": "testify -w"

Filtering tests

Tests can be filtered via regex when using the command line:
npm run test -- -f user

Coverage reporting

Install nyc and invoke it before testify. Check nyc's README for configuration options
"test": "nyc testify"

The test environment

chai describe it expect assert and sinon are available globally in tests and require files

Customizing the test environment

Required files will be executed in the node environment once jsdom mocha have been initialized.
This is useful if your scripts depend on global variables, for example:
// In required js/ts file
window.SomeGlobal = {
  someMethod: sinon.spy()
}

// In test file
describe('globals', () => {
  it('can access global', () => {
    window.SomeGlobal.someMethod('hey')
    expect(window.SomeGlobal.someMethod).calledWith('hey')
  })
})

You can also customize chai and others using the globals:
chai.use(require('chai-jquery'));

Type checking

Note that testify will not type check your files. For the sake of simplicity and speed ts-node runs in "transpile only" mode.
It's recommended to type check your project via tsc --noEmit as part of your ci and/or development process.