dotnet-testing-advanced-aspire-testing

Orchestrate AppHost containers for end-to-end integration testing of distributed .NET Aspire applications.

28|4|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/kevintsengtw/dotnet-testing-agent-skills --skill dotnet-testing-advanced-aspire-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-testing-advanced-aspire-testing
Source: https://github.com/kevintsengtw/dotnet-testing-agent-skills/tree/main/skills/dotnet-testing-advanced-aspire-testing
Command: npx skills add https://github.com/kevintsengtw/dotnet-testing-agent-skills --skill dotnet-testing-advanced-aspire-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a complete framework for integration testing of distributed .NET Aspire applications by orchestrating AppHost-based containers and ensuring all services are ready before tests run, reducing flaky tests caused by startup timing.

Core Features & Use Cases

  • AppHost-based integration tests: define and run end-to-end scenarios across multiple services (e.g., API, database, cache).
  • Migrate from Testcontainers: smooth migration path from Testcontainers to .NET Aspire Testing.
  • Lifecycle automation: manage container lifecycles with DistributedApplicationTestingBuilder and ContainerLifetime.Session for automatic cleanup after tests.
  • Test infrastructure and fixtures: sample templates and fixtures for consistent test setup across projects.

Quick Start

Follow the templates in templates/ to bootstrap Aspire Testing projects and run dotnet test against the AppHost-based integration tests.

Frequently Asked Questions about dotnet-testing-advanced-aspire-testing

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

FAQPage Schema
How do I run integration tests for .NET Aspire distributed applications?

Integration testing for .NET Aspire distributed applications is done by orchestrating AppHost containers and using test fixtures to ensure all services are ready before tests run, reducing flaky tests caused by startup timing.

What is the best way to migrate from Testcontainers to .NET Aspire testing?

Migrating from Testcontainers to .NET Aspire testing is supported by a smooth migration path that replaces direct container management with DistributedApplicationTestingBuilder for orchestrated AppHost-based end-to-end scenarios.

How do I manage container lifecycles during .NET Aspire integration testing?

Container lifecycles during .NET Aspire integration testing are managed using DistributedApplicationTestingBuilder and ContainerLifetime.Session, which handle automatic cleanup and ensure isolated, repeatable tests after completion.

Can I use collection fixtures to isolate end-to-end tests across multiple .NET Aspire services?

Collection fixtures are supported to isolate end-to-end tests across multiple .NET Aspire services, providing consistent test infrastructure and ensuring readiness checks are satisfied before executing distributed application scenarios.

Why are my distributed .NET Aspire tests failing due to container startup timing?

Distributed .NET Aspire tests often fail due to container startup timing when readiness checks are not enforced; this Skill ensures all AppHost services are ready before tests run to prevent flaky integration test results.