d707124fd9
Previously, only e2e tests were run for docs examples on CI. As a result, unit tests (which are included in the zipped archives we provide for users to download and play with the examples locally) were often outdated and broken. This commit configures specific docs examples that have meaningful unit tests to run them on CI (via the `run-example-e2e.js` script). Where necessary, the unit tests are fixed to ensure they pass and reflect the changes in the corresponding component/service. This commit also removes some auto-generated unit tests that are not meaningful (e.g. make trivial assertions, such that a component instance is truthy) and are often broken anyway (e.g. because the corresponding component has been changed in ways that make the tests fail). PR Close #36143 |
||
---|---|---|
.. | ||
app | ||
README.md | ||
e2e-spec.ts | ||
example-config.json | ||
index.html | ||
karma-test-shim.js | ||
karma.conf.js | ||
systemjs.config.1.js | ||
tsconfig.json |
README.md
This is the Angular Phonecat application adjusted to fit our boilerplate project structure.
The following changes from vanilla Phonecat are applied:
- E2E tests have been moved to the parent directory, where
run-e2e-tests
can discover and run them along with all the other examples. - Most of the phone JSON and image data removed in the interest of keeping repo weight down. Keeping enough to retain testability of the app.
Running the app
Start like any example
npm run start
Running E2E tests
Like for any example (at the project root):
gulp run-e2e-tests --filter=phonecat-3