9c55fc0f13
Currently, based on the file names it's not quite clear whether a given `.spec.ts` file runs benchmark perf or benchmark e2e functionality tests. To disambiguate these, we use new file suffixs. i.e. `e2e-spec.ts` and `perf-spec.ts`. PR Close #34753 |
||
|---|---|---|
| .. | ||
| e2e_test/old | ||
| src | ||
| BUILD.bazel | ||
| README.md | ||
| benchmark_test.bzl | ||
| e2e_test.bzl | ||
| start-server.js | ||
| tsconfig-build.json | ||
| tsconfig-e2e.json | ||
README.md
How to run the benchmarks locally
Run in the browser
yarn bazel run modules/benchmarks/src/tree/{name}:devserver
# e.g. "ng2" tree benchmark:
yarn bazel run modules/benchmarks/src/tree/ng2:devserver
Run e2e tests
# Run e2e tests of individual applications:
yarn bazel test modules/benchmarks/src/tree/ng2/...
# Run all e2e tests:
yarn bazel test modules/benchmarks/...
Use of *_aot.ts files
The *_aot.ts files are used as entry-points within Google to run the benchmark
tests. These are still built as part of the corresponding ng_module rule.