Skip to content

Commit

Permalink
Bug 1478711 - Docs: Correct out of date UI testing advice
Browse files Browse the repository at this point in the history
* The tests can now be run inside the VM.
* There is no longer a coverage report output.
  • Loading branch information
edmorley committed Jul 26, 2018
1 parent 78c2c57 commit bcffd1c
Showing 1 changed file with 4 additions and 8 deletions.
12 changes: 4 additions & 8 deletions docs/ui/installation.rst
Expand Up @@ -97,16 +97,12 @@ To run eslint by itself, you may run the lint task:
Running the unit tests
----------------------

The unit tests for the UI are run with Karma_ and Jasmine_. React components are tested with enzyme_. At this time, these tests cannot be run inside of a Vagrant VM. To run the tests:
The unit tests for the UI are run with Karma_ and Jasmine_. React components are tested with enzyme_.

* If you haven't already done so, install local dependencies by running ``yarn install`` from the project root.
* Then run the following command to execute the tests:

.. code-block:: bash
To run the tests:

$ yarn test
After the tests have finished, you can find a coverage report in the `coverage/` directory.
* If you haven't already done so, install local dependencies by running ``yarn install`` from the project root.
* Then run ``yarn test`` to execute the tests.

While working on the frontend, you may wish to watch JavaScript files and re-run tests
automatically when files change. To do this, you may run the following command:
Expand Down

0 comments on commit bcffd1c

Please sign in to comment.