fixup! doc: add more context about benchmark tests and envs used

Author: brunocroh

doc/contributing/writing-and-running-benchmarks.md

@@ -727,18 +727,41 @@ const runBenchmark = require('../common/benchmark');
 runBenchmark('buffers', { NODEJS_BENCHMARK_ZERO_ALLOWED: 1 });
 ```
 
-The environment variable `NODEJS_BENCHMARK_ZERO_ALLOWED` is necessary
-if the test runs so fast that it can result in errors or flaky tests.
-Setting this environment variable will make the benchmark ignore these issues.
-
-The way tests will be executed depends on the environment variable `NODE_RUN_ALL_BENCH_TESTS`.
-If it is set to **true**, benchmarks run with minimal iterations (`n=1`, `rounds=1`).
-The idea here is to ignore performance analysis and just check if it can run without failing.
-Despite running the minimal amount, it still consumes too much time to run
-because it needs to run all configurations.
-
-Otherwise, when `NODE_RUN_ALL_BENCH_TESTS` isn't set,
-only one configuration per benchmark is executed.
-This significantly reduces execution time but offers limited coverage
-and cannot ensure all configurations work correctly.
+The environment variable `NODEJS_BENCHMARK_ZERO_ALLOWED` is required
+when tests execute so quickly that they may produce errors or inconsistent results.
+Setting this variable instructs the benchmark to disregard such issues.
+
+Test execution behavior depends on the `NODE_RUN_ALL_BENCH_TESTS` environment variable.
+When set to **true**, benchmarks run with minimal iterations (`n=1`, `rounds=1`).
+This approach bypasses performance analysis to verify that tests can complete without failures.
+Despite the minimal iterations, execution remains time-consuming
+as all configurations must be tested.
+
+When `NODE_RUN_ALL_BENCH_TESTS` is not set,
+only a single configuration per benchmark executes.
+While this dramatically reduces execution time, it provides limited coverage
+and cannot guarantee that all configurations function properly.
+
+This PR introduce the usage of new env `NODE_RUN_ALL_BENCH_TESTS`, that can be set to all becnhmark configs run in tests to try coverage more scenarios when benchmarks can fails.
+this PR as well document how to write benchmark tests, and give more details about the envs
+
+- NODE_RUN_ALL_BENCH_TESTS
+- NODEJS_BENCHMARK_ZERO_ALLOWED
+
+Some benchmarks tests was introduced as well for benchmark groups
+
+- abort_controller
+- error
+- https
+- perf_hooks
+- permission
+- sqlite
+- test_runner
+- websocket
+
+and some incosistent test files was renamed
+
+test/benchmark/test-benchmark-async-hooks.js → test/benchmark/test-benchmark-async_hooks.js
+test/benchmark/test-benchmark-child-process.js → test/benchmark/test-benchmark-child_process.js
+
 

test/benchmark/test-benchmark-test_runner.js

@@ -4,4 +4,4 @@ require('../common');
 
 const runBenchmark = require('../common/benchmark');
 
-runBenchmark('test_runner')
+runBenchmark('test_runner');