Unit tests

.travis.yml

@@ -7,7 +7,6 @@ install:
 cache:
   directories:
     - "node_modules"
-script: 'true'
 notifications:
   email:
     recipients:

CONTRIBUTING.md

@@ -17,13 +17,17 @@ We'd also love PRs. If you're thinking of a large PR, we advise opening up an is
 ## Submitting a pull request
 
 1. [Fork][fork] and clone the repository.
-1. Configure and install the dependencies: `npm install`.
-1. Create a new branch: `git checkout -b my-branch-name`.
-1. Push to your fork and [submit a pull request][pr].
-1. Pat your self on the back and wait for your pull request to be reviewed and merged.
+2. Configure and install the dependencies: `npm install`.
+3. Make sure the tests pass on your machine: `npm test`, note: these tests also apply the linter, so there's no need to lint separately.
+4. Create a new branch: `git checkout -b my-branch-name`.
+5. Make your change, add tests, and make sure the tests still pass.
+6. Push to your fork and [submit a pull request][pr].
+7. Pat your self on the back and wait for your pull request to be reviewed and merged.
 
 Here are a few things you can do that will increase the likelihood of your pull request being accepted:
 
+- Any linting errors should be shown when running `npm test`.
+- Write and update tests.
 - Keep your changes as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
 - Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
 

jest.config.js

@@ -1,5 +1,5 @@
 module.exports = {
-  roots: ['<rootDir>/src/'],
+  roots: ['<rootDir>/src/', '<rootDir>/test/'],
   transform: {
     '^.+\\.tsx?$': 'ts-jest'
   },