Skip to content

Commit 122f1fb

Browse files
committed
chore(README): add instructions to run unit tests
1 parent daa3b3d commit 122f1fb

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

README.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,21 @@ ng build
6262
The build artifacts will be stored in the `dist/` directory.
6363

6464

65+
### Running tests
66+
67+
Before running the tests make sure that the project is built. To build the
68+
project once you can use:
69+
70+
```bash
71+
ng build
72+
```
73+
74+
With the project built in the `dist/` folder you can just run: `karma start`.
75+
Karma will run the tests and keep the browser open waiting to run again.
76+
77+
To watch the files and build them after any change you can use `ng serve`.
78+
79+
6580
### Deploying the app via GitHub Pages
6681

6782
The CLI currently comes bundled with [angular-cli-github-pages addon](https://github.com/IgorMinar/angular-cli-github-pages).
@@ -82,7 +97,7 @@ This project is currently a prototype so there are many known issues. Just to me
8297

8398
- All blueprints/scaffolds are in TypeScript only, in the future blueprints in all dialects officially supported by Angular will be available.
8499
- On Windows you need to run the `build` and `serve` commands with Admin permissions otherwise the performance really sucks.
85-
- [Karma](http://karma-runner.github.io/) and [Protractor](https://angular.github.io/protractor/) integrations are missing.
100+
- [Protractor](https://angular.github.io/protractor/) integration is missing.
86101
- The initial installation as well as `ng new` take too long because of lots of npm dependencies.
87102
- "ember" branding leaks through many error messages and help text.
88103
- Many existing ember addons are not compatible with Angular apps built via angular-cli.

0 commit comments

Comments
 (0)