fix(test-optimization): retry payload delivery failures

[juan-fernandez]

What does this PR do?

Improves retries for two Test Optimization payload delivery failures observed in Web UI end-to-end runs:

• Failures that return neither an HTTP status nor an error code receive one retry, including during finalization, without allowing an overlapping final flush to extend that retry budget.
• Each transport attempt has a total timeout starting at request creation, including local socket-queue time. Retriable final-flush attempts continue while the hard 60-second deadline has capacity.

Coded permanent failures such as ENOTFOUND remain non-retriable, and background requests retain their ordinary attempt cap.

Motivation

Web UI end-to-end runs reported endpoint_payload.requests_errors with both status_code:N/A, error_type:network and error_type:err_dd_test_optimization_request_timeout.

The existing retry classifier only retries an allowlist of coded transient network errors, while the generic network telemetry indicates the failure had no usable error code and therefore was not retried. Separately, removing the total attempt timer allowed a request waiting for a socket to remain pending until the final-flush deadline aborted it, without giving retry handling an opportunity to run.

Two full Web UI runs using the isolated retry experiment completed without payload request errors. A Web UI run using the stacked lifecycle implementation still reported request timeouts, motivating restoration of the total attempt timeout and deadline-bounded final retries in this draft.

Additional Notes

This is a draft stacked directly on #10044, which now contains both the delivery lifecycle and error telemetry changes formerly split across #10044 and #10045.

Verification:

• 59 combined Test Optimization request, telemetry, and writer tests
• ESLint on the changed production and test files
• git diff --check

[dd-octo-sts]

Overall package size

Self size: 8.44 MB
Deduped: 9.1 MB
No deduping: 9.1 MB

Dependency sizes

| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.4.0 | 127.33 kB | 447.04 kB | | opentracing | 0.14.7 | 194.81 kB | 194.81 kB | | dc-polyfill | 0.1.11 | 25.74 kB | 25.74 kB |

_{🤖 This report was automatically generated by heaviest-objects-in-the-universe}

[datadog-prod-us1-6]

 

⚠️ Warnings

⚠️ Your PR has warnings. Please review the issues below.

🚦 3 Pipeline jobs failed

Test Optimization | integration-cypress (latest, node-latest, commonJS, cypress-reporting) — ❌ 1 test failed · 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

Test run failed: timeout due to media upload endpoint failure and assertion error for string mismatch in basic-fail.js.

❌ cypress@latest commonJS reporting with agentless continues normally when the media upload endpoint fails from integration-tests/cypress/cypress-reporting.spec.js

gatherPayloadsUntilChildExit: hard timeout of 60000ms expired (child still running)
Cypress output:
Warning: The allowCypressEnv configuration option is enabled. This allows any browser code to read values from Cypress.env(). This is insecure and will be removed in a future major version.

1. Replace Cypress.env() calls with cy.env() (for sensitive values) or Cypress.expose() (for public configuration)
2. Set allowCypressEnv: false in your Cypress configuration to disable Cypress.env()

Learn more: https://on.cypress.io/cypress-env-migration


...

Test Optimization | integration-playwright (latest, node-oldest, playwright-atr) — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

1 failed test. AssertionError: Expected values to be strictly equal: 0 !== 8 at /__w/dd-trace-js/dd-trace-js/integration-tests/playwright/playwright-atr.spec.js:260:20

Test Optimization | integration-selenium (latest) — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

2 failed tests. TypeError: Cannot read properties of undefined (reading 'content') at /__w/dd-trace-js/dd-trace-js/integration-tests/selenium/selenium.spec.js:96:79

📋 Copy fix prompt

CI on my pull request is failing. Help me find and fix the root cause of each failing job below — they were flagged as caused by changes in this PR, so focus on the diff. For each job, explain the failure and propose a fix.

Before you start, set up the Datadog software-delivery tooling so you can
query the CI data yourself:

1. Check whether you already have the Datadog software-delivery MCP tools
   (e.g. a `search_datadog_ci_pipeline_events` tool) and the `unblock-pr` skill.
2. If either is missing, STOP and ask me for permission before installing
   anything. Do not install or run anything until I have said yes.
3. Only with my explicit approval, set up the Datadog software-delivery MCP
   server and skills by following:
     https://docs.datadoghq.com/getting_started/software_delivery_mcp_tools/
   then restart so the skill is picked up.
4. If I decline, skip all of the above and work from the context below alone.

Then run /unblock-pr — it will pull the CI data itself. The job context below is what we already know.

If /unblock-pr is not available — because I declined the setup above, or it did not install — work from the context below instead.

Datadog has already classified this failure as caused by changes in this PR.
Take that as given and work the fix:

1. Locate the change. Diff this branch against its base and find the change
   that produces this error. Explain the mechanism, don't just name a file:
     git fetch origin && git diff $(git merge-base origin/juan-fernandez/test-optimization-delivery-lifecycle HEAD)...HEAD
2. Reproduce it locally. Run the failing job's command or test before
   proposing anything.
3. Propose the smallest fix that addresses the root cause — not a workaround,
   not a broadened assertion, not a disabled or skipped test.
4. Re-run the same command to confirm, and say exactly what you ran.
5. If the failure turns out to be intermittent rather than deterministic, say
   so plainly instead of "fixing" it — that is a flaky test, and patching it
   hides the problem.

If the right move is to re-run the job rather than change code, use the job
link in the context below. For GitHub Actions: `gh run rerun <run-id> --failed`,
where the run ID is the number after `/runs/` in that URL (not the trailing
number, which is the job ID).

Branch: juan-fernandez/retry-unknown-test-optimization-network-errors-on-telemetry

Test Optimization | integration-cypress (latest, node-latest, commonJS, cypress-reporting)
Commit: d44b0a98a0fb2aa806e79b8eaa85d12eb886225d
Error (code / test):
2 failed tests: timeout due to media upload endpoint failure and assertion error for string mismatch in basic-fail.js.
CI job: https://github.com/DataDog/dd-trace-js/actions/runs/33420623491/job/99581824417

Test Optimization | integration-playwright (latest, node-oldest, playwright-atr)
Commit: d44b0a98a0fb2aa806e79b8eaa85d12eb886225d
Error (code / test):
1 failed test. AssertionError: Expected values to be strictly equal: 0 !== 8 at /__w/dd-trace-js/dd-trace-js/integration-tests/playwright/playwright-atr.spec.js:260:20
CI job: https://github.com/DataDog/dd-trace-js/actions/runs/33420623491/job/99581904150

Test Optimization | integration-selenium (latest)
Commit: d44b0a98a0fb2aa806e79b8eaa85d12eb886225d
Error (code / test):
2 failed tests. TypeError: Cannot read properties of undefined (reading 'content') at /__w/dd-trace-js/dd-trace-js/integration-tests/selenium/selenium.spec.js:96:79
CI job: https://github.com/DataDog/dd-trace-js/actions/runs/33420623491/job/99581886362

🧪 32 Tests failed in 4 jobs

Test Optimization | integration-cucumber — ❌ 6 tests failed

View more details · View in GitHub Actions

❌ cucumber@13.1.1 worker threads preload retries new tests from parallel workers from integration-tests/cucumber/cucumber.spec.js  

gatherPayloadsUntilChildExit: child exited with no matching payloads (after 1000ms grace period)

❌ cucumber@latest commonJS correctly calculates test code owners when working directory is not repository root from integration-tests/cucumber/cucumber.spec.js  

Cannot read properties of undefined (reading 'content')

❌ cucumber@latest commonJS forwards telemetry from parallel workers from integration-tests/cucumber/cucumber.spec.js  

Cannot read properties of undefined (reading 'content')

↳ and 3 more — View all

Test Optimization | integration-cypress — ❌ 5 tests failed

View more details · View in GitHub Actions

❌ cypress@12.0.0 commonJS reporting with agentless continues normally when the media upload endpoint fails from integration-tests/cypress/cypress-reporting.spec.js  

gatherPayloadsUntilChildExit: hard timeout of 60000ms expired (child still running)
Cypress output:
[13526:0831/174630.061988:ERROR:node_bindings.cc(279)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[13526:0831/174630.062059:ERROR:node_bindings.cc(279)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[13526:0831/174630.062067:ERROR:node_bindings.cc(279)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[13526:0831/174630.062072:ERROR:node_bindings.cc(279)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[13526:0831/174630.062078:ERROR:node_bindings.cc(279)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[13680:0831/174630.485554:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
Missing baseUrl in compilerOptions. tsconfig-paths will be skipped

...

❌ cypress@12.0.0 esm reporting with agentless continues normally when the media upload endpoint fails from integration-tests/cypress/cypress-reporting.spec.js  

gatherPayloadsUntilChildExit: hard timeout of 60000ms expired (child still running)
Cypress output:
[13091:0831/174636.510582:ERROR:node_bindings.cc(279)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[13091:0831/174636.510645:ERROR:node_bindings.cc(279)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[13091:0831/174636.510653:ERROR:node_bindings.cc(279)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[13091:0831/174636.510659:ERROR:node_bindings.cc(279)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[13091:0831/174636.510665:ERROR:node_bindings.cc(279)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[13245:0831/174636.924938:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
Missing baseUrl in compilerOptions. tsconfig-paths will be skipped

...

❌ cypress@14.5.4 commonJS reporting with agentless continues normally when the media upload endpoint fails from integration-tests/cypress/cypress-reporting.spec.js  

gatherPayloadsUntilChildExit: hard timeout of 60000ms expired (child still running)
Cypress output:
[14487:0831/174643.263796:ERROR:node_bindings.cc(379)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[14487:0831/174643.263867:ERROR:node_bindings.cc(379)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[14487:0831/174643.263874:ERROR:node_bindings.cc(379)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[14487:0831/174643.263879:ERROR:node_bindings.cc(379)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.
[14487:0831/174643.263885:ERROR:node_bindings.cc(379)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.

DevTools listening on ws://127.0.0.1:44717/devtools/browser/81dfc7e6-4616-437e-923e-f24305e84c0c
Missing baseUrl in compilerOptions. tsconfig-paths will be skipped
...

↳ and 2 more — View all

Test Optimization | integration-playwright — ❌ 19 tests failed

View more details · View in GitHub Actions

❌ playwright@1.38.0 failure screenshots reports upload errors without changing the Playwright result from integration-tests/playwright/playwright-reporting.spec.js  

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 1 failed
    [chromium] › failure-screenshot-test.js:43:1 › uploads only the automatic failure screenshot ───
  1 skipped
  1 passed (2.7s)

❌ playwright@1.61.0 failure screenshots reports upload errors without changing the Playwright result from integration-tests/playwright/playwright-reporting.spec.js  

gatherPayloadsUntilChildExit: hard timeout of 60000ms expired (child still running)
Playwright output:
Error [ERR_REQUIRE_ESM]: require() of ES Module /tmp/006a14c310d201f3/5c2fd85ff726f6f9/node_modules/oxc-parser/src-js/index.js from /tmp/006a14c310d201f3/5c2fd85ff726f6f9/node_modules/dd-trace/packages/datadog-instrumentations/src/helpers/rewriter/compiler.js not supported.
Instead change the require of index.js in /tmp/006a14c310d201f3/5c2fd85ff726f6f9/node_modules/dd-trace/packages/datadog-instrumentations/src/helpers/rewriter/compiler.js to a dynamic import() which is available in all CommonJS modules.
    at Hook.Module.require (/tmp/006a14c310d201f3/5c2fd85ff726f6f9/node_modules/dd-trace/packages/dd-trace/src/ritm.js:121:31)
    at Object.parse (/tmp/006a14c310d201f3/5c2fd85ff726f6f9/node_modules/dd-trace/packages/datadog-instrumentations/src/helpers/rewriter/compiler.js:20:19)
    at parse (/tmp/006a14c310d201f3/5c2fd85ff726f6f9/node_modules/dd-trace/packages/datadog-instrumentations/src/helpers/rewriter/compiler.js:70:32)
    at injectAsyncEndCallbackWait (/tmp/006a14c310d201f3/5c2fd85ff726f6f9/node_modules/dd-trace/packages/datadog-instrumentations/src/helpers/rewriter/transforms.js:146:26)
    at waitForAsyncEnd (/tmp/006a14c310d201f3/5c2fd85ff726f6f9/node_modules/dd-trace/packages/datadog-instrumentations/src/helpers/rewriter/transforms.js:117:3)
    at #p (/tmp/006a14c310d201f3/5c2fd85ff726f6f9/node_modules/dd-trace/vendor/dist/@apm-js-collab/code-transformer/index.js:1:3129)
...

❌ playwright@latest failure screenshots does not warn when the active transport can upload screenshots from integration-tests/playwright/playwright-reporting.spec.js  

Expected values to be strictly equal:

0 !== 1

↳ and 16 more — View all

Test Optimization | integration-selenium — ❌ 2 tests failed

View more details · View in GitHub Actions

❌ selenium 4.11.0 with cucumber identifies tests using selenium as browser tests from integration-tests/selenium/selenium.spec.js  

Cannot read properties of undefined (reading 'content')

❌ selenium latest with cucumber identifies tests using selenium as browser tests from integration-tests/selenium/selenium.spec.js  

Cannot read properties of undefined (reading 'content')

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

🔄 Datadog retried 34 tests - 1 passed on retry

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 3b9a84b | Docs | View more details | Give us feedback!}

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-08-31 17:49:26

Comparing candidate commit 3b9a84b in PR branch juan-fernandez/retry-unknown-test-optimization-network-errors-on-telemetry with baseline commit cd47b29 in branch juan-fernandez/test-optimization-delivery-lifecycle.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 2294 metrics, 16 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:debugger-enabled-but-breakpoint-not-hit-20

• unstable cpu_user_time [-395.172ms; +636.685ms] or [-4.377%; +7.051%]
• unstable execution_time [-392.778ms; +636.453ms] or [-4.348%; +7.046%]
• unstable throughput [-1776273.787op/s; +1094096.533op/s] or [-6.396%; +3.940%]

scenario:debugger-line-probe-with-snapshot-minimal-24

• unstable max_rss_usage [-13.992MB; +17.443MB] or [-5.643%; +7.035%]

scenario:dogstatsd-aggregated-26

• unstable execution_time [-74.098ms; +31.443ms] or [-7.208%; +3.059%]

scenario:dogstatsd-with-tags-20

• unstable cpu_user_time [-268.170ms; +351.309ms] or [-5.497%; +7.201%]
• unstable execution_time [-267.627ms; +351.322ms] or [-5.396%; +7.084%]
• unstable throughput [-125512.801op/s; +95347.894op/s] or [-7.424%; +5.640%]

scenario:plugin-cassandra-driver-long-query-26

• unstable cpu_user_time [-174.900ms; +226.623ms] or [-4.710%; +6.103%]
• unstable execution_time [-176.944ms; +224.678ms] or [-4.649%; +5.903%]

scenario:plugin-graphql-long-with-depth-and-collapse-off-20

• unstable max_rss_usage [-19.884MB; +37.149MB] or [-5.099%; +9.526%]

scenario:plugin-graphql-long-with-depth-off-20

• unstable max_rss_usage [-5737.201KB; +7544.058KB] or [-4.593%; +6.039%]

scenario:plugin-graphql-long-with-depth-on-max-20

• unstable cpu_user_time [-671.722ms; +796.367ms] or [-5.788%; +6.863%]
• unstable execution_time [-691.646ms; +812.610ms] or [-5.838%; +6.859%]
• unstable throughput [-4.373op/s; +3.923op/s] or [-6.435%; +5.772%]

scenario:test-optimization-large-suite-20

• unstable max_rss_usage [-4022.290KB; +3897.956KB] or [-5.090%; +4.933%]

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (juan-fernandez/test-optimization-delivery-lifecycle@cd47b29). Learn more about missing BASE report.

Additional details and impacted files

@@                                  Coverage Diff                                   @@
##             juan-fernandez/test-optimization-delivery-lifecycle   #10069   +/-   ##
======================================================================================
  Coverage                                                       ?   98.12%           
======================================================================================
  Files                                                          ?      992           
  Lines                                                          ?   149626           
  Branches                                                       ?    12835           
======================================================================================
  Hits                                                           ?   146821           
  Misses                                                         ?     2805           
  Partials                                                       ?        0           

Flag	Coverage Δ
aiguard	62.57% <65.95%> (?)
aiguard-integration	59.17% <70.21%> (?)
apm-bucket-0	62.00% <65.95%> (?)
apm-bucket-1	67.56% <65.95%> (?)
apm-bucket-2	67.14% <65.95%> (?)
apm-bucket-3	63.81% <65.95%> (?)
apm-capabilities-tracing	62.55% <84.61%> (?)
apm-integrations-aerospike	59.82% <65.95%> (?)
apm-integrations-confluentinc-kafka-javascript	66.13% <65.95%> (?)
apm-integrations-couchbase	60.36% <65.95%> (?)
apm-integrations-http	65.80% <65.95%> (?)
apm-integrations-kafkajs	66.72% <65.95%> (?)
apm-integrations-next	63.32% <65.95%> (?)
apm-integrations-prisma	61.42% <65.95%> (?)
appsec	76.61% <80.85%> (?)
appsec-express_fastify_graphql	73.04% <65.95%> (?)
appsec-integration	49.26% <76.59%> (?)
appsec-kafka_ldapjs_lodash	67.10% <65.95%> (?)
appsec-mongodb-core_mongoose_mysql	70.38% <65.95%> (?)
appsec-next	56.66% <65.95%> (?)
appsec-node-serialize_passport_postgres	69.83% <65.95%> (?)
appsec-sourcing_stripe_template	68.22% <65.95%> (?)
debugger	68.95% <78.72%> (?)
instrumentations-bucket-0	55.15% <65.95%> (?)
instrumentations-bucket-1	63.66% <65.95%> (?)
instrumentations-bucket-10	64.90% <65.95%> (?)
instrumentations-bucket-11	65.55% <65.95%> (?)
instrumentations-bucket-12	55.03% <65.95%> (?)
instrumentations-bucket-13	55.32% <65.95%> (?)
instrumentations-bucket-14	55.16% <65.95%> (?)
instrumentations-bucket-2	56.24% <65.95%> (?)
instrumentations-bucket-3	57.06% <65.95%> (?)
instrumentations-bucket-4	63.11% <65.95%> (?)
instrumentations-bucket-5	49.35% <65.95%> (?)
instrumentations-bucket-6	65.00% <65.95%> (?)
instrumentations-bucket-7	55.30% <65.95%> (?)
instrumentations-bucket-8	62.47% <65.95%> (?)
instrumentations-bucket-9	57.87% <65.95%> (?)
instrumentations-instrumentation-couchbase	53.70% <65.95%> (?)
instrumentations-integration-esbuild	34.41% <23.68%> (?)
llmobs-ai_anthropic_bedrock	66.37% <65.95%> (?)
llmobs-bucket-1	64.48% <65.95%> (?)
llmobs-openai	66.35% <65.95%> (?)
llmobs-openai-agents_vertex-ai	63.53% <65.95%> (?)
llmobs-sdk	75.80% <80.85%> (?)
openfeature	59.75% <31.91%> (?)
openfeature-unit	57.52% <65.95%> (?)
platform-core_esbuild_instrumentations-misc	40.56% <65.95%> (?)
platform-integration	64.52% <74.46%> (?)
platform-shimmer_unit-guardrails_webpack	38.30% <65.95%> (?)
plugins-browser-bunyan_bullmq_cassandra	65.79% <65.95%> (?)
plugins-bucket-0	60.42% <65.95%> (?)
plugins-bucket-1	57.66% <23.68%> (?)
plugins-bucket-11	66.28% <65.95%> (?)
plugins-bucket-18	65.80% <65.95%> (?)
plugins-bucket-19	64.41% <65.95%> (?)
plugins-bucket-20	66.28% <65.95%> (?)
plugins-bucket-4	60.60% <65.95%> (?)
plugins-cookie_cookie-parser_crypto	54.70% <65.95%> (?)
plugins-fastify_fetch_fs	64.97% <65.95%> (?)
plugins-generic-pool_google-cloud-pubsub_grpc	68.57% <65.95%> (?)
plugins-handlebars_hapi_hono	63.01% <65.95%> (?)
plugins-ioredis_knex_langgraph	61.08% <65.95%> (?)
plugins-ldapjs_light-my-request_limitd-client	62.73% <65.95%> (?)
plugins-lodash_mariadb_memcached	63.35% <65.95%> (?)
plugins-moleculer_mongodb_mongodb-core	65.65% <65.95%> (?)
plugins-mongoose_multer_mysql	63.45% <65.95%> (?)
plugins-mysql2_nats_node-serialize	65.64% <65.95%> (?)
plugins-opensearch_passport-http_pino	63.47% <65.95%> (?)
plugins-postgres_process_pug	62.56% <65.95%> (?)
plugins-redis_router_sequelize	66.24% <65.95%> (?)
plugins-test-and-upstream-rhea_undici_url	65.59% <65.95%> (?)
plugins-valkey_vm_winston	61.87% <65.95%> (?)
plugins-ws	63.87% <65.95%> (?)
profiling	65.90% <78.72%> (?)
serverless-aws-sdk-aws-sdk	54.84% <65.95%> (?)
serverless-aws-sdk-base-inject-field	54.28% <65.95%> (?)
serverless-aws-sdk-bedrockruntime	57.57% <65.95%> (?)
serverless-aws-sdk-client	59.41% <65.95%> (?)
serverless-aws-sdk-dynamodb	58.52% <65.95%> (?)
serverless-aws-sdk-eventbridge	57.09% <65.95%> (?)
serverless-aws-sdk-kinesis	62.60% <65.95%> (?)
serverless-aws-sdk-lambda	60.52% <65.95%> (?)
serverless-aws-sdk-s3	58.58% <65.95%> (?)
serverless-aws-sdk-serverless-peer-service	63.18% <65.95%> (?)
serverless-aws-sdk-sns	63.51% <65.95%> (?)
serverless-aws-sdk-sqs	63.98% <65.95%> (?)
serverless-aws-sdk-stepfunctions	58.39% <65.95%> (?)
serverless-aws-sdk-util	54.95% <65.95%> (?)
serverless-bucket-0	57.10% <31.91%> (?)
serverless-bucket-1	63.15% <65.95%> (?)
test-optimization-cucumber	63.81% <75.32%> (?)
test-optimization-cypress	63.81% <81.39%> (?)
test-optimization-jest	72.09% <98.80%> (?)
test-optimization-mocha	71.94% <83.11%> (?)
test-optimization-playwright-playwright-atr	58.69% <58.33%> (?)
test-optimization-playwright-playwright-efd	60.22% <80.95%> (?)
test-optimization-playwright-playwright-final-status	59.83% <80.95%> (?)
test-optimization-playwright-playwright-impacted-tests	60.01% <82.14%> (?)
test-optimization-playwright-playwright-test-management	61.02% <80.95%> (?)
test-optimization-playwright-playwright-test-span	59.74% <92.85%> (?)
test-optimization-selenium	58.27% <86.90%> (?)
test-optimization-vitest	72.54% <80.51%> (?)
test-optimization-vitest-browser	58.50% <72.72%> (?)
test-optimization-webdriverio	65.09% <68.83%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.