Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README.md #3018

Closed
wants to merge 5 commits into from
Closed

Update README.md #3018

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
47b77a9
Update README.md
Mathou54 Nov 4, 2016
e51bcc8
Update README.md
Mathou54 Nov 5, 2016
4bdb97c
Merge branch 'master' into master
Mathou54 Nov 5, 2016
a5e8af1
Merge branch 'master' into master
Mathou54 Nov 7, 2016
f68f0b6
Merge branch 'master' into master
Mathou54 Nov 8, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 5 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,11 @@ or `ng serve --prod` will also make use of uglifying and tree-shaking functional
ng test
```

Tests will execute after a build is executed via [Karma](http://karma-runner.github.io/0.13/index.html), and it will automatically watch your files for changes. You can run tests a single time via `--watch=false`.
Tests will execute after a build is executed via [Karma](http://karma-runner.github.io/0.13/index.html), and it will automatically watch your files for changes. You can run tests a single time via `--watch=false`.

You can run tests with coverage via `--code-coverage`. The coverage report will be in the `coverage/` directory.

Linting during tests is also available via the `--lint` flag. See [Linting and formatting code](#linting-and-formatting-code) chapter for more informations.

### Running end-to-end tests

Expand Down