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 |
||
---|---|---|
.. | ||
class_bindings | ||
expanding_rows | ||
js-web-frameworks | ||
largeform | ||
largetable | ||
old | ||
styling | ||
tree | ||
views | ||
BUILD.bazel | ||
README.md | ||
bootstrap_ng2.ts | ||
bootstrap_plain.ts | ||
util.ts |
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
.