[Debugger] Add system-test coverage for the debugger guardrails by dudikeleti · Pull Request #7287 · DataDog/system-tests

Introduce initial debugger guardrail coverage for capture incomplete reasons and evaluation timeout behavior, with new rows disabled in manifests until tracer support is ready.

dudikeleti

committed

Adds debugger guardrail coverage for snapshot size trimming and capture timeout reporting. 1MB snapshot cap and notCapturedReason=timeout behavior.

dudikeleti

committed

Adds the guardrail RFC link to the new debugger test classes and removes the setup-time negative snapshot wait so evaluation-timeout assertions rely on collected scenario output instead of a fixed …

dudikeleti

committed

Address review feedback on the debugger guardrail tests

dudikeleti

committed

fix ci

dudikeleti

committed

Validate the established `truncated` flag instead of requiring an unsupported `notCapturedReason`.

dudikeleti

committed

validate timeout reporting on the intended captured collection without relying on runner timing.

dudikeleti

committed

Enable debugger capture-timeout coverage across tracers

dudikeleti

committed

Make debugger capture-timeout guardrail deterministic

dudikeleti

committed

fix formatting

dudikeleti

committed

Strengthen debugger guardrail test validation

dudikeleti

committed

test(debugger): make capture timeout guardrail deterministic

dudikeleti

committed

test(debugger): use a 10ms cross-tracer capture timeout

dudikeleti

committed

Harden debugger guardrail test assertions

dudikeleti

committed

Move debugger capture-timeout support to weblog metadata

dudikeleti

committed

Exclude post-migration capture-timeout scenario from legacy matrix check

dudikeleti

committed

address copilot comment

dudikeleti

committed

fix lint

dudikeleti

committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[Debugger] Add system-test coverage for the debugger guardrails#7287

[Debugger] Add system-test coverage for the debugger guardrails#7287
dudikeleti wants to merge 18 commits into
mainfrom
dudik/debugger/guardrails-tests

Commits on Jul 16, 2026

Introduce initial debugger guardrail coverage for capture incomplete reasons and evaluation timeout behavior, with new rows disabled in manifests until tracer support is ready.

Adds debugger guardrail coverage for snapshot size trimming and capture timeout reporting. 1MB snapshot cap and notCapturedReason=timeout behavior.

Adds the guardrail RFC link to the new debugger test classes and removes the setup-time negative snapshot wait so evaluation-timeout assertions rely on collected scenario output instead of a fixed …

Address review feedback on the debugger guardrail tests

fix ci

Validate the established `truncated` flag instead of requiring an unsupported `notCapturedReason`.

validate timeout reporting on the intended captured collection without relying on runner timing.

Enable debugger capture-timeout coverage across tracers

Make debugger capture-timeout guardrail deterministic

fix formatting

Strengthen debugger guardrail test validation

test(debugger): make capture timeout guardrail deterministic

test(debugger): use a 10ms cross-tracer capture timeout

Harden debugger guardrail test assertions

Move debugger capture-timeout support to weblog metadata

Exclude post-migration capture-timeout scenario from legacy matrix check

address copilot comment

fix lint