Run E2E tests locally using the new-e2e framework with Pulumi-based infrastructure
npx skills add https://github.com/DataDog/datadog-agent --skill run-e2e
Run E2E tests from test/new-e2e/tests/ using dda inv new-e2e-tests.run.
$ARGUMENTS to determine what to run. The user may provide:windows/install-test, agent-platform/upgrade, containers)TestInstall, TestUpgrade)test/new-e2e/ to targets, so targets must be relative to that directory (e.g., ./tests/agent-subcommands/flare, NOT ./test/new-e2e/tests/...)agent-subcommands/flare, use ./tests/agent-subcommands/flare as --targetstest/new-e2e/tests/ using Glob, then strip the test/new-e2e/ prefix for the targetTest), 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 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.
$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)run_in_background for the Bash tool since e2e tests are long-running.The following must be configured before running e2e tests:
pulumi CLI installed~/.test_infra_config.yaml exists with proper configurationIf any prerequisite is missing, inform the user what needs to be set up.
Tests are organized under test/new-e2e/tests/, running ls test/new-e2e/tests should give the list of test packages
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
# 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.
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.
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
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
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
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.
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.
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.
Take datadog/run-e2e from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.