Graham/angular-cli
1
0
Fork 0
mirror of https://github.com/angular/angular-cli.git synced 2025-05-17 11:03:53 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: update testing chapter with general test commands

Browse Source 
Closes: #18710
This commit is contained in:
Jefiozie 2020-09-07 11:38:38 +02:00 committed by Alan Agius
parent 6ac67f84c3
commit b2f0f074bf
2 changed files with 26 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
README.md
View File

@ -115,18 +115,20 @@ as expected.
There are three different test suites which can be run locally: There are three different test suites which can be run locally:
* Unit tests ### Unit tests
* Run: `yarn test --full` * Run all tests: `yarn bazel test //packages/...`
* Debug: `yarn debug:test --full` * Run a subset of the tests, use the full Bazel target example: `yarn bazel test //packages/schematics/angular:angular_test`
* Large tests * For a complete list of test targets use the following Bazel query: `yarn bazel query "tests(//packages/...)"`
* Run: `yarn test-large --full`
* Debug: `yarn debug:test-large --full`
* End to end tests
* Run: `node tests/legacy-cli/run_e2e.js`
* Run subset of tests: `node tests/legacy-cli/run_e2e.js tests/legacy-cli/e2e/tests/i18n/ivy-localize-*`
When running the debug commands, Node will stop and wait for a debugger to You can find more info about debugging [tests with Bazel in the docs.]
attach. You can attach your IDE to the debugger to stop on breakpoints and step through the code. Also see [IDE Specific Usage](#ide-specific-usage) for a (https://github.com/angular/angular-cli/blob/master/docs/process/bazel.md#debugging-jasmine_node_test)
### End to end tests
* Run: `node tests/legacy-cli/run_e2e.js`
* Run a subset of the tests: `node tests/legacy-cli/run_e2e.js tests/legacy-cli/e2e/tests/i18n/ivy-localize-*`
When running the debug commands, Node will stop and wait for a debugger to attach.
You can attach your IDE to the debugger to stop on breakpoints and step through the code. Also, see [IDE Specific Usage](#ide-specific-usage) for a
simpler debug story. simpler debug story.
When debugging a specific test, change `describe()` or `it()` to `fdescribe()` When debugging a specific test, change `describe()` or `it()` to `fdescribe()`

24
scripts/templates/readme.ejs
View File

@ -123,18 +123,20 @@ as expected.
There are three different test suites which can be run locally: There are three different test suites which can be run locally:
* Unit tests ### Unit tests
* Run: `yarn test --full` * Run all tests: `yarn bazel test //packages/...`
* Debug: `yarn debug:test --full` * Run a subset of the tests, use the full Bazel target example: `yarn bazel test //packages/schematics/angular:angular_test`
* Large tests * For a complete list of test targets use the following Bazel query: `yarn bazel query "tests(//packages/...)"`
* Run: `yarn test-large --full`
* Debug: `yarn debug:test-large --full`
* End to end tests
* Run: `node tests/legacy-cli/run_e2e.js`
* Run subset of tests: `node tests/legacy-cli/run_e2e.js tests/legacy-cli/e2e/tests/i18n/ivy-localize-*`
When running the debug commands, Node will stop and wait for a debugger to You can find more info about debugging [tests with Bazel in the docs.]
attach. You can attach your IDE to the debugger to stop on breakpoints and step through the code. Also see [IDE Specific Usage](#ide-specific-usage) for a (https://github.com/angular/angular-cli/blob/master/docs/process/bazel.md#debugging-jasmine_node_test)
### End to end tests
* Run: `node tests/legacy-cli/run_e2e.js`
* Run a subset of the tests: `node tests/legacy-cli/run_e2e.js tests/legacy-cli/e2e/tests/i18n/ivy-localize-*`
When running the debug commands, Node will stop and wait for a debugger to attach.
You can attach your IDE to the debugger to stop on breakpoints and step through the code. Also, see [IDE Specific Usage](#ide-specific-usage) for a
simpler debug story. simpler debug story.
When debugging a specific test, change `describe()` or `it()` to `fdescribe()` When debugging a specific test, change `describe()` or `it()` to `fdescribe()`