// 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.
| name | e2e-test-runner |
| description | 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. |
| 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
Fetch the latest CAF abbreviations page from Microsoft Learn and compare against resourceDefinition.json official.slug values. Reports drift where the provider's slug differs from the official CAF slug. Triggers on: weekly scheduled audit, manual sync check.
Discover new Azure resources by fetching the latest azurerm provider resource list from the Terraform Registry and comparing against resourceDefinition.json. Identifies unsupported resources. Triggers on: weekly scheduled discovery, manual audit.
Update CHANGELOG.md with a new entry under the correct section. Parses existing structure, adds entries under [Unreleased], and assesses semver impact. Triggers on: after resource changes, bug fixes, documentation updates, or any notable project change.
Provide step-by-step guidance for contributors based on their contribution type. References CONTRIBUTING.md and project conventions. Triggers on: new contributor questions, 'how do I contribute', contribution guidance requests.
Run test coverage analysis (make test_coverage), parse coverage percentage, compare against the 95% threshold, and flag regressions. Triggers on: PR checks, post-build validation, release prep.
Ensure documentation files under docs/resources/ and docs/data-sources/ reflect current resource types with accurate examples. Triggers on: after adding/updating resources, documentation audit.