honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
angular-cn/modules/benchmarks/src
History
Paul Gschwendtner 4d88b4bc26 ci: do not run benchmark measurements in circleci (#34753) 
Currently we run all benchmark perf tests in CircleCI. Since we do not
collect any results, we unnecessarily waste CI/RBE resources. Instead,
we should just not run benchmark perf tests in CI, but still run the
functionality e2e tests which ensure that benchmarks are not broken.

We can do this by splitting the perf and e2e tests into separate
files/targets.

PR Close #34753
2020-01-29 09:22:27 -08:00
..
class_bindings
build: set default ts_devserver serving_path to /app_bundle.js to match g3 (#33996)
2019-11-26 16:09:32 -08:00
expanding_rows
build: set default ts_devserver serving_path to /app_bundle.js to match g3 (#33996)
2019-11-26 16:09:32 -08:00
js-web-frameworks
perf: rename index to index_aot (#34258)
2019-12-05 13:10:48 -08:00
largeform
ci: do not run benchmark measurements in circleci (#34753)
2020-01-29 09:22:27 -08:00
largetable
ci: do not run benchmark measurements in circleci (#34753)
2020-01-29 09:22:27 -08:00
old
perf: don't create holey arrays (#32155)
2019-08-21 08:27:43 -07:00
styling
refactor(ivy): Switch styling to new reconcile algorithm (#34616)
2020-01-24 12:23:00 -08:00
tree
ci: do not run benchmark measurements in circleci (#34753)
2020-01-29 09:22:27 -08:00
views
build: set default ts_devserver serving_path to /app_bundle.js to match g3 (#33996)
2019-11-26 16:09:32 -08:00
bootstrap_ng2.ts
feat(core): upgrade rxjs to 6.0.0-alpha.4 (#22573)
2018-03-19 21:51:51 -07:00
bootstrap_plain.ts
refactor(benchmarks): refactor to support AOT bootstrap in G3 (#12075)
2016-10-04 16:27:45 -07:00
BUILD.bazel
style: enforce buildifier lint on CI (#28186)
2019-02-26 16:57:41 -08:00
README.md
build(bazel): //modules/benchmarks/src/largetable/render3:perf bazel protractor test (#24788)
2018-07-24 08:26:16 -07:00
util.ts
perf: report cold and minimal times when profiling in a browser (#33653)
2019-11-07 20:30:59 +00:00

README.md

Benchmark Directory Layout

Bazel

Under bazel the rules for laying out test files are slightly different. Use largetable/render3 as an example.

Put the perf file in current subdirectory (ie largetable) such that the same perf file can be used for each of the sub-subdirectories. (ie largetable/* should all be testable with the same perf file largetable/largetable_perf.spec.ts). Under bazel, typescript protractor spec files must end with .spec.ts or .test.ts.