.github/skills/e2e-test-runner/SKILL.md
Run end-to-end tests (make test_e2e or make test_e2e_quick), parse results, and produce a structured summary. Use after build succeeds to validate real Terraform workflows. Triggers on: post-build validation, PR checks, release verification.
npx skillsauth add aztfmod/terraform-provider-azurecaf e2e-test-runnerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Scope | Command | Duration | When to use |
|-------|---------|----------|-------------|
| Quick | make test_e2e_quick | ~10-15s | Every change, fast feedback |
| Full | make test_e2e | ~25-30s | PR validation, pre-release |
| Data source | make test_e2e_data_source | ~10s | Data source changes |
| Naming | make test_e2e_naming | ~15s | Naming convention changes |
| Import | make test_e2e_import | ~10s | Import functionality changes |
Default to quick unless the caller specifies otherwise.
make test_e2e_quick 2>&1 | tee /tmp/e2e-output.txt
Check exit code and extract test results:
grep -E "^(ok|FAIL|---)" /tmp/e2e-output.txt
If all tests pass:
✅ E2E tests: PASSED (<scope>)
Tests: <count> passed
Duration: <time>
If failures detected:
❌ E2E tests: FAILED (<scope>)
Failed tests:
- <test_name>: <failure summary>
Details:
<relevant output>
rm -f /tmp/e2e-output.txt
development
Analyze test failure output to identify root cause and suggest fixes. Use when build or test failures occur. Triggers on: test failures, build errors, CI failures.
development
Validate a resource definition end-to-end using terraform test with mock_provider azurerm. Proves the CAF-generated name is accepted by the azurerm provider schema without Azure credentials. Use after provider-build-test succeeds to run the mocked azurerm integration test.
documentation
Analyze changes since the last release tag and determine the appropriate semantic version bump (patch/minor/major) based on CHANGELOG entries and commit types. Triggers on: release preparation, version planning.
testing
Compare two versions of resourceDefinition.json (e.g., branch vs main) and produce a structured change summary. Triggers on: PR review, audit, before/after comparison.