You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is recommended to create a new test file when a new benchmark is introduced
@@ -777,24 +769,33 @@ only a single configuration per benchmark executes.
777
769
While this dramatically reduces execution time, it provides limited coverage
778
770
and cannot guarantee that all configurations function properly.
779
771
780
-
This PR introduces the usage of a new environment variable `NODE_RUN_ALL_BENCH_TESTS`, which can be set to run all benchmark configurations in tests to cover more scenarios where benchmarks might fail.
772
+
This PR introduces the usage of a new environment variable `NODE_RUN_ALL_BENCH_TESTS`,
773
+
which can be set to run all benchmark configurations in tests to cover more scenarios where benchmarks might fail.
781
774
This PR also documents how to write benchmark tests and provides more details about the environment variables:
782
775
783
-
*NODE_RUN_ALL_BENCH_TESTS
784
-
*NODEJS_BENCHMARK_ZERO_ALLOWED
776
+
*NODE\_RUN\_ALL\_BENCH\_TESTS
777
+
*NODEJS\_BENCHMARK\_ZERO\_ALLOWED
785
778
786
779
Benchmark tests were added for the following groups:
787
780
788
-
*abort_controller
781
+
*abort\_controller
789
782
* error
790
783
* https
791
-
*perf_hooks
784
+
*perf\_hooks
792
785
* permission
793
786
* sqlite
794
-
*test_runner
787
+
*test\_runner
795
788
* websocket
796
789
797
790
Additionally, some inconsistent test files were renamed:
0 commit comments