The next chapters presents some requirements related to your unit tests (using Karma).
@@ -81,6 +81,8 @@ the Angular template expects the following in your `karma.conf.js`:
],
},
```
:warning: in case of multiple angular projects in the workspace, each project shall produce its coverage report in `reports/ng-coverage-<projectName>.cobertura.xml` (it can be in sub-folders but must follow the file name pattern).
3. Additionally, if using SonarQube, you may also want to generate [LCOV report](https://docs.sonarqube.org/latest/analysis/test-coverage/javascript-typescript-test-coverage/):
```js
coverageReporter:{
@@ -120,6 +122,8 @@ In order to be able to [integrate your test reports to GitLab](https://docs.gitl
...
}
```
:warning: in case of multiple Angular projects in the workspace, each project shall produce its JUnit report either in `reports/ng-test-<projectName>.xunit.xml` or `reports/<projectName>/ng-test.xunit.xml`.
Additionally, if using **SonarQube**, you may also want to generate [SonarQube generic test report](https://docs.sonarqube.org/latest/analysis/generic-test/):
@@ -183,11 +187,11 @@ The Angular template features a `ng-publish` job to publish the built project.
This job is bound to the `publish` stage, and uses the following variable:
| `NG_PUBLISH_ENABLED` | Set variable to `true` to enable the publish job | none (disabled) |
| `NG_PUBLISH_PROJECTS` | Space separated list of projects to publish | If no project is specified, the value of _angular.json_ `defaultProject` property is used |
| `NG_PUBLISH_PROJECTS`| Space separated list of projects to publish | If no project is specified, all workspace projects are published |
"description":"Space separated list of projects to publish. If no project is specified, the value of _angular.json_ `defaultProject` property is used",
"description":"Space separated list of projects to publish. If no project is specified, all workspace projects are published.",