Skip to content

Commit

Permalink
Fix instructions for running libtextsecure tests
Browse files Browse the repository at this point in the history
  • Loading branch information
EvanHahn-Signal authored and josh-signal committed Aug 28, 2020
1 parent 7aff568 commit 373ea0d
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -176,10 +176,10 @@ Please write tests! Our testing framework is
The easiest way to run all tests at once is `yarn test`.

You can browse tests from the command line with `grunt unit-tests` or in an
interactive session with `NODE_ENV=test yarn run start`. The `libtextsecure` tests are run
similarly: `grunt lib-unit-tests` and `NODE_ENV=test-lib yarn run start`. You can tweak
the appropriate `test.html` for both of these runs to get code coverage numbers via
`blanket.js` (it's shown at the bottom of the web page when the run is complete).
interactive session with `NODE_ENV=test yarn run start`.

If you want to run the `libtextsecure` tests, you can run `yarn run test-electron`,
which also runs the unit tests.

To run Node.js tests, you can run `yarn test-server` from the command line. You can get
code coverage numbers for this kind of run via `yarn test-server-coverage`, then display
Expand Down

0 comments on commit 373ea0d

Please sign in to comment.