Reorganize "Testing" pages
- Nov 01, 2017
- Oct 31, 2017
-
-
totten authored
I'd like to be able to merge the general, incremental improvements for the "Testing" section, but these two new pages aren't yet written. Comment them out.
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
* Provide a better visualization of the the different test suites * Migrate setup instructions from https://github.com/civicrm/civicrm-core/blob/master/tests/README.md
-
totten authored
-
totten authored
1. Add new entries for Protractor, Codeception, and QUnit 2. This menu includes (a) some pages about the overall testing process and (b) some pages about specific tools. Consistently put the general before the specific.
-
totten authored
-
totten authored
-
totten authored
There are multiple tools for testing in JS. We'll want separate pages for each.
-
totten authored
The second statement doesn't make much sense without the first statement. Put them together.
-
totten authored
-
totten authored
Running civilint is important for any/all code. Seems a bit arbitrary emphasizing this point specifically for tests.
-
totten authored
-
totten authored
-