This project was generated with Angular CLI version 11.2.8.

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.

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.

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.

Run ng test to execute the unit tests via Karma.

Run ng e2e to execute the end-to-end tests via Protractor.

1. To begin, add the angular-cli-ghpages builder.

ng add angular-cli-ghpages

2. If you’re deploying the project to a Github project page you’ll need to set the baseHref property as the repository name. The baseHref will be used for all relative URLs on your site. You could specify the baseHref as part of the project architect deploy options in the angular.json file. Or just pass it as the --base-href flag to the ng deploy command. If you’re deploying the project to a Github user page, you do not need to set this option.

ng deploy --base-href=/<repository-name>/

GitHub will automatically enable Pages when you push a gh-pages branch. There is no need to enable Pages from the repository settings.

ng deploy --base-href=/ng-dev-testing/

• Source
• How to deploy a React, Angular and Vue project to Github pages
• Mocking Route params in Angular unit tests
• Testing Angular routing components with the RouterTestingModule
• Writing Angular Test Cases for Router, Service, ActivatedRoute
• Mock ActivatedRoute with params, data and snapshot
• An Introduction to Jasmine Unit Testing
• Overriding Components for Testing

To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.