aspire-integration-testing

Write xUnit integration tests for .NET Aspire applications with real dependencies.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill aspire-integration-testing-agibuild
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-integration-testing
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/aspire-integration-testing
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill aspire-integration-testing-agibuild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of writing robust integration tests for .NET Aspire applications by leveraging xUnit and Aspire's testing facilities, ensuring your distributed applications function correctly with real dependencies.

Core Features & Use Cases

  • Real Dependency Testing: Test against actual infrastructure like databases and message brokers orchestrated by Aspire.
  • Dynamic Endpoint Discovery: Automatically find service endpoints, avoiding hardcoded URLs.
  • Fixture Management: Utilize IAsyncLifetime for proper setup and teardown of test environments.
  • Use Case: You need to verify that your ASP.NET Core API correctly interacts with a real PostgreSQL database and a Redis cache, all managed within a .NET Aspire application, before deploying to production.

Quick Start

Use the aspire-integration-testing skill to set up a test fixture for your .NET Aspire application.

Frequently Asked Questions about aspire-integration-testing

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

FAQPage Schema
How do I test .NET Aspire apps with real dependencies like databases and message brokers?

Dynamic endpoint discovery in .NET Aspire integration testing automatically finds service endpoints during test execution. This mechanism avoids hardcoded URLs by resolving service addresses dynamically within your xUnit test fixtures orchestrated by Aspire.Hosting.Testing.

How do I manage test fixture setup and teardown for .NET Aspire integration tests?

You manage fixture setup and teardown for .NET Aspire integration tests by utilizing the IAsyncLifetime interface. This provides proper lifecycle management for your test environments, ensuring distributed resources orchestrated by Aspire are correctly initialized and cleaned up.

Do I need xUnit to run integration tests for .NET Aspire distributed applications?

Yes, you need xUnit to run integration tests for .NET Aspire distributed applications. The testing framework requires both Aspire.Hosting.Testing and xUnit for executing test cases and asserting outcomes against real dependencies within your distributed environment.

What is the best way to verify service-to-service communication in a .NET Aspire application?

The best way to verify service-to-service communication in a .NET Aspire application is running integration tests against real infrastructure. Using xUnit and Aspire.Hosting.Testing validates actual interactions between ASP.NET Core APIs, databases, and message brokers orchestrated by Aspire.