mcpbeat Sign in

Run E2e Agent Skill

Run E2E tests locally using the new-e2e framework with Pulumi-based infrastructure

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3695
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/DataDog/datadog-agent --skill run-e2e

What it tells the agent to use

found in the instruction text
Bash runs shell commands — read the instruction before connecting

The instruction itself

5 sections, as written by the author

Run E2E tests from test/new-e2e/tests/ using dda inv new-e2e-tests.run.

Instructions

  • Parse $ARGUMENTS to determine what to run. The user may provide:
  • A test directory path (e.g., windows/install-test, agent-platform/upgrade, containers)
  • A test function name (e.g., TestInstall, TestUpgrade)
  • Flags to pass through (see below)
  • A combination of the above
  • Resolve the test target:
  • The invoke task automatically prepends test/new-e2e/ to targets, so targets must be relative to that directory (e.g., ./tests/agent-subcommands/flare, NOT ./test/new-e2e/tests/...)
  • If the user gives a directory like agent-subcommands/flare, use ./tests/agent-subcommands/flare as --targets
  • If the user gives a partial name, search for matching directories under test/new-e2e/tests/ using Glob, then strip the test/new-e2e/ prefix for the target
  • If the user gives a test function name (starts with Test), find which package contains it using Grep under test/new-e2e/tests/, then set --targets to the package path (relative to test/new-e2e/) and --run to the test name
  • If ambiguous, list the matching options and ask the user to pick one
  • Build the command:
   dda inv new-e2e-tests.run --targets=./tests/<path> [flags]

IMPORTANT: --targets paths are relative to test/new-e2e/. Do NOT include test/new-e2e/ in the target path.

  • Supported flags (pass through from $ARGUMENTS):
  • --run <regex> — Only run tests matching this regex
  • --skip <regex> — Skip tests matching this regex
  • --keep-stack — Keep infrastructure up after test (for debugging)
  • --configparams <key=value> — Override Pulumi ConfigMap parameters
  • --agent-image <image:tag> — Use a specific agent image
  • --cluster-agent-image <image:tag> — Use a specific cluster agent image
  • --stack-name-suffix <suffix> — Add suffix to stack name (useful for stuck stacks)
  • --verbose / --no-verbose — Toggle verbose output (default: verbose)
  • --max-retries <n> — Retry failed tests up to n times
  • --flavor <flavor> — Package flavor (e.g., "datadog-agent")
  • --cache — Enable test cache (disabled by default)
  • Before running, confirm the full command with the user.
  • Run the command with a 60-minute timeout (infrastructure provisioning can take a while). Use run_in_background for the Bash tool since e2e tests are long-running.
  • After completion, summarize the results: which tests passed, which failed, and any useful error output.

Prerequisites

The following must be configured before running e2e tests:

  • pulumi CLI installed
  • ~/.test_infra_config.yaml exists with proper configuration

If any prerequisite is missing, inform the user what needs to be set up.

Available Test Suites

Tests are organized under test/new-e2e/tests/, running ls test/new-e2e/tests should give the list of test packages

Issues when running tests

If the test was previously executed and that the infra is in a weird state, that Pulumi is not aware of, trying to rerun the test with the same stack can lead to strange error, like resource being replaced, while they should not exist at all yet.

To avoid that issue it is possible to execute the test with a stack with a different name, using --stack-name-suffix <suffix>, please use short stack name suffix.

Stop the execution early when you detect that issue in the logs

Examples

# Run all tests in a directory
dda inv new-e2e-tests.run --targets=./tests/windows/install-test

# Run a specific test
dda inv new-e2e-tests.run --targets=./tests/agent-platform/tests/upgrade --run TestUpgrade

# Keep stack for debugging
dda inv new-e2e-tests.run --targets=./tests/containers --run TestContainerLinux --keep-stack

# Run with specific agent image
dda inv new-e2e-tests.run --targets=./tests/agent-platform/tests --agent-image "my-registry/agent:latest"

# Run with stack name suffix
dda inv new-e2e-tests.run --targets=./tests/windows/install-test --stack-name-suffix 2



## Usage

- `/run-e2e windows/install-test` — Run all Windows install tests
- `/run-e2e windows/install-test --run TestInstall` — Run only TestInstall
- `/run-e2e TestUpgrade` — Auto-find and run TestUpgrade
- `/run-e2e agent-platform --keep-stack` — Run with stack kept alive

## Output

Show the user the full command before running, then report test results when done.

Other skills for the same job

different authors, same section of the catalogue
Webapp Testing
by anthropics
vendor ×12

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

6k tokens scripts
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Systematic Debugging
by ratacat
×7

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

10k tokens scripts
Verification Before Completion
by ZhanlinCui
×6

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

1k tokens
Backtest Expert
by BaggaT236
×3

Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.

15k tokens scripts
Adaptyv
by christophacham
×3

Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.

16k tokens
Aeon
by christophacham
×3

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.

19k tokens

How to use it

Copy the folder

Take datadog/run-e2e from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.