Add instructions on how to run Jasmine JS tests on the 'Running Unit Tests' page.
Review Request #8637 — Created Jan. 20, 2017 and submitted
There are two types of tests that can be run to check changes or new modules, before posting code for review. Prior to this change, the 'Running Unit Tests' page only contained instructions on how to run tests on Python work. This change adds instruction for how to run unit tests on work done in JavaScript.
Built the change and reviewed the resulting information and formatting on web browser.
| Description | From | Last Updated |
|---|---|---|
|
I'm not certain if "front-end" and "back-end" are the right separation here - since where does a template fall? Front-end … |
 mike_conley
|
|
|
Instead of repeating this instruction, we should instead direct the user to the Getting Started guide that shows how to … |
mike_conley
|
|
|
"depending on if you are running a test on if" is a little awkward. Perhaps this should be: "There are … |
mike_conley
|
|
|
Note the capital S in JavaScript. |
mike_conley
|
|
|
Got some trailing whitespace here, I'm afraid. Can you please remove it? |
mike_conley
|
|
|
Can you fix this so the hyphens are the same width as the text? |
 david
|
|
|
should be "the JavaScript tests" (since it runs all of them). |
david
|
|
|
This should have a trailing / at the end of the URL. |
david
|
|
|
Here too. |
david
|
|
|
We shouldn't be encoding a link to the docs on the Review Board website. Instead, in docs/codebase/getting-started.rst, next to the … |
david
|
- Bugs:
-
-
I'm not certain if "front-end" and "back-end" are the right separation here - since where does a template fall? Front-end or back-end?
Perhaps we should instead have a distinction between server tests and JavaScript tests?
-
Instead of repeating this instruction, we should instead direct the user to the Getting Started guide that shows how to boot the development server.
So maybe something like:
To run a JavaScript test, first launch the web server, then browse to http://localhost:8080/js-tests. The full JavaScript test suite should run automatically.
- Commit:
-
83f09c1d7fb2564c3bd04535155589a2fd52c2b067f7fe84804d709f81257d3e35bdd565ce128876
- Diff:
-
Revision 2 (+21 -1)
-
Tool: Pyflakes Ignored Files: docs/codebase/unit-tests/running-tests.rst Tool: PEP8 Style Checker Ignored Files: docs/codebase/unit-tests/running-tests.rst
- Commit:
-
67f7fe84804d709f81257d3e35bdd565ce1288766cca86a3e268b5ee84680e342ab70c952bdeb100
- Diff:
-
Revision 3 (+20 -1)
-
Tool: PEP8 Style Checker Ignored Files: docs/codebase/unit-tests/running-tests.rst Tool: Pyflakes Ignored Files: docs/codebase/unit-tests/running-tests.rst
- Description:
-
There are two types of tests that can be run to check changes or new modules,
before posting code for review. Prior to this change, the 'Running Unit Tests' ~ page only contained instructions on how to run tests on back-end work. This ~ change adds instruction for how to run the Jasmine JS tests for fron-end work. ~ page only contained instructions on how to run tests on Python work. This ~ change adds instruction for how to run unit tests on work done in JavaScript.
- Commit:
-
6cca86a3e268b5ee84680e342ab70c952bdeb100322019ebfdc0c639223a1b39423302f38be6adf5
- Diff:
-
Revision 4 (+20 -1)
-
Tool: PEP8 Style Checker Ignored Files: docs/codebase/unit-tests/running-tests.rst Tool: Pyflakes Ignored Files: docs/codebase/unit-tests/running-tests.rst
-
-
We shouldn't be encoding a link to the docs on the Review Board website. Instead, in docs/codebase/getting-started.rst, next to the "Development Web Server" section, we can add an anchor:
.. _development-web-serverand then for the link in the text, we can do:
... under :ref:`development-web-server`It might be nice to do the same for "Getting Started" (replace that text with :ref:`getting-started`)
Tool: Pyflakes Ignored Files: docs/codebase/unit-tests/running-tests.rst Tool: PEP8 Style Checker Ignored Files: docs/codebase/unit-tests/running-tests.rst