7fb3cc07de
Creates anew integratin test for `ng-update` migrations. The integration test uses an Angular CLI project that will be updated using the latest package output symlinked from then `./dist/packages-dist`. This allows us to ensure that migrations work in real CLI projects. Another big benefit is that the Angular version is updated to the latest. This is something we couldn't replicate in unit tests but is extremely important. It's important because compilation could break with newer Angular versions (note that migrations are always executed after the new angular version has been installed). PR Close #32349
28 lines
1.0 KiB
Markdown
28 lines
1.0 KiB
Markdown
# NgUpdateMigrations
|
|
|
|
This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.0.0-beta.15.
|
|
|
|
## Development server
|
|
|
|
Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.
|
|
|
|
## Code scaffolding
|
|
|
|
Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.
|
|
|
|
## Build
|
|
|
|
Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `--prod` flag for a production build.
|
|
|
|
## Running unit tests
|
|
|
|
Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).
|
|
|
|
## Running end-to-end tests
|
|
|
|
Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).
|
|
|
|
## Further help
|
|
|
|
To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
|