deployment-e2e-testing

Run real Azure deployments and verify Aspire endpoints in CI workflows.

6.2k|952|Updated Sep 25, 2023
One-click install
npx skills add https://github.com/microsoft/aspire --skill deployment-e2e-testing-microsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-e2e-testing
Source: https://github.com/microsoft/aspire/tree/main/.agents/skills/deployment-e2e-testing
Command: npx skills add https://github.com/microsoft/aspire --skill deployment-e2e-testing-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

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/.

Frequently Asked Questions about deployment-e2e-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Aspire Azure deployments end-to-end?

Aspire Azure deployment end-to-end validation runs real Azure deployments and verifies deployed endpoints actually work. This catches broken deployment changes by testing distributed applications against real Azure infrastructure instead of just checking if the deployment command succeeds.

What's the best way to automate Aspire CLI commands for deployment testing?

Hex1b-driven terminal automation runs the Aspire CLI deterministically by automating prompts the same way a user would. This ensures consistent execution of aspire new and aspire deploy flows across CI-nightly, manual, and deploy-test workflows for distributed applications.

Does Aspire end-to-end testing support OIDC authentication in CI pipelines?

Aspire end-to-end testing supports OIDC authentication in CI and Azure CLI authentication locally, with clear skip behavior when auth is unavailable. This dual approach ensures deployment tests run seamlessly across both automated pipeline and local development environments.

How do I ensure Azure resources are cleaned up after deployment testing?

Azure resource cleanup after deployment testing is guaranteed by enforcing unique resource group management and removing resources in a finally block. This operational guardrail prevents orphaned Azure infrastructure and controls cloud costs during repeated end-to-end test runs.

Can I run deployment E2E tests manually outside of CI workflows?

Deployment E2E tests can run manually by ensuring Azure CLI authentication is available, then executing the test project under tests/Aspire.Deployment.EndToEnd.Tests/. The Skill applies to manual workflows just as it does to CI-nightly and deploy-test automated pipelines.

How do I debug failed Aspire deployment tests?

Failed Aspire deployment tests are debugged using generated recordings and GitHub step summary reporting. These operational guardrails capture terminal automation interactions and deployment outputs, providing the exact context needed to diagnose broken Azure deployment scenarios.