Boomerang has a suite of performance tests to ensure code changes do not introduce performance regressions.
The performance tests reside in
To run the performance tests:
This should run all suites in
tests/perf/ and will save the results in
tests/perf/results/metrics.json: Results of each test
tests/perf/results/[scenario].[test]: Raw results for each test
tests/perf/results/baseline.json: Baseline comparison file (
Comparing to a Baseline
To compare performance results to a baseline, you first need to run this on the "before" codebase:
This will create
Then, you can run performance tests against the "current" code by executing:
This will create a new
tests/perf/results/metrics.json each run, and will compare those results to
$ grunt perf-compare --diff-only Running "perf-compare" task Results comparison to baseline: 00-basic.00-empty.page_load_time : 28 -1 (-4%) 00-basic.00-empty.mark_fire_event_before_beacon_called : [missing in baseline] Done.