File tree Expand file tree Collapse file tree 1 file changed +16
-1
lines changed Expand file tree Collapse file tree 1 file changed +16
-1
lines changed Original file line number Diff line number Diff line change @@ -62,6 +62,21 @@ ng build
62
62
The build artifacts will be stored in the ` dist/ ` directory.
63
63
64
64
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
+
65
80
### Deploying the app via GitHub Pages
66
81
67
82
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
82
97
83
98
- All blueprints/scaffolds are in TypeScript only, in the future blueprints in all dialects officially supported by Angular will be available.
84
99
- 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.
86
101
- The initial installation as well as ` ng new ` take too long because of lots of npm dependencies.
87
102
- "ember" branding leaks through many error messages and help text.
88
103
- Many existing ember addons are not compatible with Angular apps built via angular-cli.
You can’t perform that action at this time.
0 commit comments