What problem does it solve?
Aspire deployment changes are hard to verify locally, so this Skill helps you catch broken deployments by running real end-to-end tests against Azure infrastructure.
Core Features & Use Cases
- Azure-backed E2E validation: Deploy Aspire apps to real Azure resources and verify endpoints actually work.
- Deterministic terminal automation: Use Hex1b-driven prompt/terminal automation to run the Aspire CLI the same way a user would.
- CI- and local-ready authentication: Supports OIDC authentication in CI and Azure CLI authentication locally, with clear skip behavior when auth is unavailable.
- Operational guardrails: Enforces unique resource groups, GitHub step summary reporting, recording generation for debugging, and reliable cleanup in a finally block.
Use case: You’re adding a new Azure deployment scenario (or changing deployment parameters) and want confidence that the resulting Azure-hosted services respond correctly, not just that the deployment command succeeds.
Quick Start
Run a deployment E2E test by ensuring Azure authentication is available, then execute the test project that includes DeploymentE2E tests under tests/Aspire.Deployment.EndToEnd.Tests/.