Write E2e

Write end-to-end tests for the Datadog Agent using the test/e2e-framework/ framework.

Parse $ARGUMENTS to determine what to test.

Where to find what you need

| What | Where | Read first? |

|------|-------|:---:|

| E2E test writing guidelines and rules | test/new-e2e/codereview_guideline.md | ✅ |

| Framework API (environments, provisioners, agentparams) | test/e2e-framework/AGENTS.md | ✅ |

| Fakeintake API (payload types, client methods, extending) | test/fakeintake/AGENTS.md | ✅ |

| Setup, prerequisites, running tests | docs/public/how-to/test/e2e.md | |

| Real tests to use as patterns | test/new-e2e/tests/ (see lookup table in e2e-framework AGENTS.md) | |

| Check system overview | root AGENTS.md § "Check System" | |

| Test placement / team ownership | CODEOWNERS | |

| CI job definitions | .gitlab/test/e2e/e2e.yml, .gitlab/windows/test/e2e/windows.yml | |

| CI trigger rules | .gitlab-ci.yml (search for .on_*_or_e2e_changes) | |

| Examples | test/new-e2e/examples/ | |

Read every file marked "Read first?" before writing any test. Browse examples and a few real tests

that match your use case. Make sure to follow _all_ the guidelines specified.

Checklist

• Read the feature's implementation to understand what payloads it sends
• Check if E2E tests already exist under test/new-e2e/tests/
• Place tests in the right <area> directory (check CODEOWNERS);

one file per platform target (e.g., disk_nix_test.go, disk_win_test.go)

• Verify compilation: cd test/new-e2e && go vet ./tests/<area>/...
• Run the test locally before pushing — compilation alone is not enough:

dda inv new-e2e-tests.run --targets=./tests/<area>/...

See test/e2e-framework/AGENTS.md § "Validating E2E tests" if it fails

• Check CI wiring: grep -n 'TARGETS:.*<area>' .gitlab/test/e2e/e2e.yml

Output

Show the user: files created, how to compile-check, how to run locally

(dda inv new-e2e-tests.run --targets=./tests/<area>/...), and whether

CI changes are needed.