message: Add notes to contrib file about testing and code coverage
diff: @@ -61,15 +61,21 @@ meets these guidelines:
  1. The pull request should include tests, either as doctests,
  unit tests, or both.
  -2. If the pull request adds functionality, the docs should be updated
  +2. Run `npm run lint` and resolve all errors. Run `npm run test` and
  + resolve all test failures.
  +3. Check code coverage by running the following commands in the `assets`
  + directory. Run `npm run cover` to check code coverage on `.js` work, and
  + run `nosetests --with-coverage` to check code coverage on `.py` work. You
  + may have to first run `pip install nose coverage`.
  +4. If the pull request adds functionality, the docs should be updated
  as part of the same PR. Doc string are often sufficient, make
  sure to follow the sphinx compatible standards.
  -3. The pull request should work for Python 2.7, and ideally python 3.4+.
  +5. The pull request should work for Python 2.7, and ideally python 3.4+.
  ``from __future__ import`` will be required in every `.py` file soon.
  -4. Code will be reviewed by re running the unittests, flake8 and syntax
  +6. Code will be reviewed by re running the unittests, flake8 and syntax
  should be as rigorous as the core Python project.
  -5. Please rebase and resolve all conflicts before submitting.
  -6. If you are asked to update your pull request with some changes there's
  +7. Please rebase and resolve all conflicts before submitting.
  +8. If you are asked to update your pull request with some changes there's
  no need to create a new one. Push your changes to the same branch.
  ## Documentation
  