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
@@ -742,24 +734,33 @@ only a single configuration per benchmark executes.
742
734
While this dramatically reduces execution time, it provides limited coverage
743
735
and cannot guarantee that all configurations function properly.
744
736
745
-
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.
737
+
This PR introduces the usage of a new environment variable `NODE_RUN_ALL_BENCH_TESTS`,
738
+
which can be set to run all benchmark configurations in tests to cover more scenarios where benchmarks might fail.
746
739
This PR also documents how to write benchmark tests and provides more details about the environment variables:
747
740
748
-
*NODE_RUN_ALL_BENCH_TESTS
749
-
*NODEJS_BENCHMARK_ZERO_ALLOWED
741
+
*NODE\_RUN\_ALL\_BENCH\_TESTS
742
+
*NODEJS\_BENCHMARK\_ZERO\_ALLOWED
750
743
751
744
Benchmark tests were added for the following groups:
752
745
753
-
*abort_controller
746
+
*abort\_controller
754
747
* error
755
748
* https
756
-
*perf_hooks
749
+
*perf\_hooks
757
750
* permission
758
751
* sqlite
759
-
*test_runner
752
+
*test\_runner
760
753
* websocket
761
754
762
755
Additionally, some inconsistent test files were renamed:
0 commit comments