القائمة
Run Windows E2E tests (MSI install tests or Fleet Automation/installer tests) locally against AWS-provisioned VMs
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/DataDog/datadog-agent --skill run-windows-e2eيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Monitor the current PR's GitLab pipeline to completion, then report success or investigate a failure. Use when the user asks to follow, babysit, watch, or wait on a PR/pipeline, or just after pushing to / creating a PR.
Classify a failed CI as either caused by an active incident, flakiness, or a true code regression. Use when a PR's pipeline is red and it isn't obvious whether the PR's own changes are at fault. Trigger phrases include: - "investigate this CI failure" - "please fix CI" - "why did this job fail" - "is there an incident affecting CI" - "should I retry this" This should also be invoked whenever the user asks you to investigate _or fix_ a failing CI, to ensure we don't spend hours trying to fix something broken upstream.
Write or extend Datadog Agent new-e2e tests, including fakeintake coverage and the GitLab wiring that runs them; derives scope from the current diff when no target is named. Not for running tests that already exist (run-e2e, run-windows-e2e), or for judging whether a behavior belongs in E2E at all (e2e-audit).
| name | run-windows-e2e |
| description | Run Windows E2E tests (MSI install tests or Fleet Automation/installer tests) locally against AWS-provisioned VMs |
| allowed-tools | Bash, Read, Glob, Grep, AskUserQuestion |
| argument-hint | [suite] [TestFunctionName] [--build release|pipeline|local] [--pipeline-id <id>] [--version <version>] |
Run Windows E2E tests from test/new-e2e/tests/windows/ or test/new-e2e/tests/installer/windows/.
Detailed reference material lives in references/ next to this file — read the
relevant one when a step calls for it rather than duplicating it here:
references/setup.md — prerequisites, ~/.test_infra_config.yaml, dev modereferences/running.md — setup-env, local builds, go test flagsreferences/vm-access.md — connecting to a dev-mode VM (RDP/SSH)references/troubleshooting.md — test outputs, Pulumi locks, AWS profile$ARGUMENTSDetermine:
install-test, service-test, agent-package, install-script). If not provided, ask the user.TestXxx function. Most suites expect exactly one test per run — ask the user which one if not specified.--build pipeline (default), --build local, or --build release; pass --pipeline-id <id> through if given.setup-env run with --prefix STABLE_AGENT in Step 3 (see references/running.md "Upgrade tests").--branch <name> to setup-env. The default is the current git branch, which may have no pipelines if it's a local feature branch.Map suite names to Go package paths:
| Suite | Package path |
|---|---|
install-test | ./test/new-e2e/tests/windows/install-test |
service-test | ./test/new-e2e/tests/windows/service-test |
fips-test | ./test/new-e2e/tests/windows/fips-test |
domain-test | ./test/new-e2e/tests/windows/domain-test |
| installer / Fleet Automation (agent-package, install-script, install-exe, ddot, apm-inject, …) | ./test/new-e2e/tests/installer/windows |
The installer / Fleet Automation tests are all one flat package (the
suites/<package>/ subdirectories were flattened in #47161) — pick the area by
test function with -run (e.g. TestAgentUpgrades, TestInstallScript,
TestDDOTExtensionViaMSI, TestAPMInjectInstalls).
If the user gives a partial name or test function, search with Glob/Grep under test/new-e2e/tests/windows/ and test/new-e2e/tests/installer/windows/ to resolve it.
test -f ~/.test_infra_config.yaml && echo "EXISTS" || echo "MISSING"
pulumi version 2>/dev/null || echo "MISSING"
If either is missing, offer to run dda inv e2e.setup and wait for the user to
complete its interactive prompts. If prerequisites exist but devMode is not
set, mention that devMode: true reuses VMs across runs (much faster for
iterative development). Full detail in references/setup.md.
Run setup-env with --fmt json to capture the required env vars (no shell
eval needed — prepend the parsed pairs inline to go test in Step 5).
# From a pipeline (most common)
dda inv new-e2e-tests.setup-env --build pipeline --fmt json [--branch <branch>] [--pipeline-id <id>]
# From a local build (run `dda inv msi.build` first, + `msi.package-oci` for installer/OCI tests)
dda inv new-e2e-tests.setup-env --build local --fmt json
For upgrade tests, run a second time with --prefix STABLE_AGENT and merge the
vars in. GitLab token handling, local-build details, and the STABLE_AGENT
flow are in references/running.md.
If devMode: true and the user is rerunning, the previous VM may still have the
agent installed. Ask whether they've cleaned up (MSI tests: uninstall the agent;
installer tests: datadog-installer.exe purge). See
references/running.md "Clean state between runs".
go test commandgo test -v -timeout 30m -tags test <package-path> -run <TestFunction>$
Two rules to apply (rationale in references/running.md):
anchor the -run regex with $ at both suite and subtest level, and use the
exact package path with no trailing /... (or output won't stream).
Show the full command to the user and confirm before running.
Warn the user that AWS SSO auth may open a browser window when the test starts
(the test pauses until login completes), and that a non-sandbox AWS_PROFILE
will cause auth errors — advise unset AWS_PROFILE.
Run with run_in_background: true since tests provision real AWS VMs.
Provisioning takes a few minutes; once the VM is up, SSH becomes available
within ~60s (Linux) / ~180s (Windows). If SSH is not available within those
windows, troubleshoot before assuming the test is still running normally
(see references/vm-access.md).
When the test completes:
~/e2e-output/latest/ (crash dumps, agent/installer logs, event logs). If devMode is on, the VM is still up — offer to help RDP/SSH in via references/vm-access.md.references/troubleshooting.md.