mstest-integration-test

Standardize MSTest integration tests for .NET Minimal API endpoints.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/a35506322/Lab.Todo --skill mstest-integration-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mstest-integration-test
Source: https://github.com/a35506322/Lab.Todo/tree/main/.cursor/skills/mstest-integration-test
Command: npx skills add https://github.com/a35506322/Lab.Todo --skill mstest-integration-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent and unstandardized integration testing practices for .NET Minimal API projects, reducing flaky tests and ensuring API endpoints function correctly end-to-end.

Core Features & Use Cases

  • Standardized Test Structure: Provides a consistent folder layout and naming convention for integration test classes, making test suites easy to navigate and maintain.
  • Reusable Test Setup: Includes pre-built patterns for initializing test web application factories, authenticating test clients, and managing test lifecycle with MSTest attributes.
  • Tooling Integration: Supports NSubstitute for mocking dependencies and Entity Framework Core InMemory for isolated database testing without external infrastructure.
  • Use Case: When you add a new CRUD endpoint to a .NET Todo API, use this Skill to generate both individual endpoint tests and full flow tests that cover the entire request lifecycle.

Quick Start

Use the mstest-integration-test skill to generate a complete integration test class for a new Todo API endpoint following the project's standardized patterns.

Frequently Asked Questions about mstest-integration-test

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

FAQPage Schema
How do I structure integration tests for .NET Minimal API projects using MSTest?

To structure .NET Minimal API integration tests with MSTest, use a standardized folder layout and naming convention for test classes, applying pre-built patterns for initializing test web application factories and managing test lifecycles to ensure maintainable suites.

Can I use EF Core InMemory with NSubstitute for isolated .NET API integration testing?

Yes, you can use EF Core InMemory for isolated database testing and NSubstitute for mocking dependencies during .NET API integration testing, eliminating the need for external infrastructure while validating full CRUD flows and endpoint behavior.

What is the best way to reduce flaky tests when validating .NET API endpoints end-to-end?

Reducing flaky tests in .NET API endpoint validation requires standardizing integration test implementation with consistent setup patterns, reusable test web application factories, and isolated environments using EF Core InMemory and NSubstitute to improve reliability.

How do I generate full CRUD flow tests for a new .NET Todo API endpoint?

Generating full CRUD flow tests for a .NET Todo API endpoint involves applying standardized MSTest patterns to create both individual endpoint tests and request lifecycle tests, utilizing pre-built initialization setups for consistent validation.

Does MSTest integration testing support authenticating test clients for .NET Minimal APIs?

Yes, MSTest integration testing for .NET Minimal APIs includes pre-built patterns for authenticating test clients, allowing you to securely validate protected endpoints and manage the test lifecycle using MSTest attributes within a standardized structure.