OpenParable
Skip to content
← Back to skills

Write E2e

Testing & Quality
write-e2e

Write E2e is an Agent Skill for testing & quality published in the DataDog/datadog-agent repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Write E2E tests for the Datadog Agent using the new-e2e framework with fakeintake assertions

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/DataDog/datadog-agent/blob/HEAD/.claude/skills/write-e2e/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/write-e2e, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

WhatWhere
Framework API (environments, provisioners, agentparams)test/e2e-framework/AGENTS.md
Fakeintake API (payload types, client methods, extending)test/fakeintake/AGENTS.md
Setup, prerequisites, running testsdocs/public/how-to/test/e2e.md
Real tests to use as patternstest/new-e2e/tests/ (see lookup table in e2e-framework AGENTS.md)
Check system overviewroot AGENTS.md § "Check System"
Test placement / team ownershipCODEOWNERS
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)
Examplestest/new-e2e/examples/

Read the first two files before writing any test. Browse examples and a few real tests that match your use case.

Checklist

  1. Read the feature's implementation to understand what payloads it sends
  2. Check if E2E tests already exist under test/new-e2e/tests/
  3. Place tests in the right <area> directory (check CODEOWNERS); one file per platform target (e.g., disk_nix_test.go, disk_win_test.go)
  4. Verify compilation: cd test/new-e2e && go vet ./tests/<area>/...
  5. 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
  6. 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.