mcpbeat

Run E2e Tests

azure/run-e2e-tests

Run end-to-end (E2E) tests - provider test suites or upstream Karpenter tests, with focus filtering, background execution, and monitoring

335 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
552
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/Azure/karpenter-provider-azure --skill run-e2e-tests

The instruction itself

6 sections, as written by the author

E2E Tests

Running Tests

  • Provider tests: TEST_SUITE=<suite> make az-e2etests (suites in test/suites/)
  • Upstream tests: FOCUS=<focus> make az-upstream-e2etests (source in Go module cache or upstream repo)

Use FOCUS to filter further (or FDescribe/FIt in code).

Background Execution

Run with nohup so tests continue even if you run other commands or the terminal disconnects:

TEST_SUITE=Consolidation nohup make az-e2etests > /workspaces/karpenter/logs/e2e.log 2>&1 &

Codespace Considerations

Idle suspension kills all processes (default 30min, can be increased under https://github.com/settings/codespaces; only affects new codespaces). Logs in /workspaces (not /tmp) survive for checking after resume.

Monitoring

  • Logs: tail -f <logfile> (or tail -n for spot check)
  • Cluster: kubectl get nodeclaims,nodes,pods -w
  • Events: make az-kevents
  • Azure resources: make az-res
  • Metrics: port-forward to Karpenter pod, /metrics endpoint

GitHub Actions

Run via .github/workflows/e2e.yaml using gh workflow run.

How to use it

Copy the folder

Take azure/run-e2e-tests 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.