test: clarify [0,1] range for system.cpu.utilization metric test

The <=1 should fix flakiness. The <=0 test might make this flaky again. Refs: #73
elastic · Mar 14, 2024 · 1dc577a · 1dc577a
1 parent df99425
commit 1dc577a
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/packages/opentelemetry-node/test/host-metrics.test.js b/packages/opentelemetry-node/test/host-metrics.test.js
@@ -45,11 +45,11 @@ const testFixtures = [
                     'data points are present in system.cpu.utilization metric'
                 );
                 const allInRange = metric.gauge?.dataPoints.every(
-                    (dp) => dp.asDouble < 1
+                    (dp) => 0 <= dp.asDouble && dp.asDouble <= 1
                 );
                 t.ok(
                     allInRange,
-                    '"system.cpu.utilization" data points have a value between 0-1'
+                    '"system.cpu.utilization" data points are in the range [0,1]'
                 );
                 if (!allInRange) {
                     // Note: extra output to debug flaky test (https://github.com/elastic/elastic-otel-node/issues/73).