Results for “xunit-test-patterns”

Write effective unit tests with XUnit, covering standard and data-driven testing approaches.

Get best practices for XUnit unit testing, including data-driven tests

Write effective unit tests with TUnit, covering standard tests, data-driven tests, and migration from xUnit.

Reference for test filter syntax across VSTest and MTP platforms, covering MSTest, NUnit, xUnit v3, and TUnit frameworks with examples and translation guidance.

Write effective unit tests with NUnit, covering standard and data-driven testing approaches.

xUnit.net testing framework with Fact, Theory, fixtures, DI, and mocking with Moq and NSubstitute. Covers .NET testing best practices. USE WHEN: user mentions "xUnit", ".NET testing", "Fact", "Theory", "InlineData", "Moq", "NSubstitute", "C# unit test" DO NOT USE FOR: NUnit - use `nunit`, Vitest - use `vitest`, Jest - use `jest`, Playwright - use `playwright`

Get best practices for NUnit unit testing, including data-driven tests

Write and organize F# tests using xUnit, FsUnit, Unquote, FsCheck for property-based testing, and integration test patterns with ASP.NET Core and Testcontainers.

NUnit testing framework with TestCase, SetUp/TearDown, assertions, and parameterized tests for .NET applications. USE WHEN: user mentions "NUnit", "TestCase", "TestFixture", "NUnit assertions", "NUnit parameterized tests", ".NET NUnit" DO NOT USE FOR: xUnit - use `xunit`, MSTest, JavaScript testing frameworks

Write, review, or refactor C# unit tests using XUnit v3, NSubstitute, FluentAssertions, and Atc.Test. Use this skill whenever the user asks to create tests, add test coverage, fix failing tests, mock dependencies with NSubstitute, or follow the ClassName_MethodUnderTest_ExpectedBehavior naming convention in a .NET/C# project.

Get best practices for TUnit unit testing, including data-driven tests

Migrates .NET test projects from xUnit.net v2 to xUnit.net v3, updating package references, project files, and code to compile and pass tests.

Detects the test platform (VSTest vs Microsoft.Testing.Platform) and test framework (MSTest, xUnit, NUnit, TUnit) from .NET project files.

Migrate .NET test projects from xUnit.net (v2 or v3) to MSTest v4, converting attributes, assertions, fixtures, and project configuration.

F# 测试模式——xUnit、FsUnit、Unquote、FsCheck 基于属性的测试、集成测试及覆盖率

Get best practices for JUnit 5 unit testing, including data-driven tests

.NET backend conventions, patterns, and test infrastructure. Use when working with C# files, .csproj projects, ASP.NET APIs, xUnit tests, FluentAssertions, Entity Framework, WebApplicationFactory, dotnet CLI, NuGet packages, .NET dependency injection, middleware, or controller patterns.

使用 xUnit、FluentAssertions、模拟、集成测试和测试组织最佳实践的 C# 和 .NET 测试模式。

Run, filter, or troubleshoot .NET tests with `dotnet test`, detecting the test platform (VSTest vs Microsoft.Testing.Platform) and framework to apply the correct command syntax.

Audits test files for anti-patterns and quality issues, producing a severity-ranked report across multiple languages and frameworks.

Write effective unit tests with JUnit 5, covering standard and data-driven testing approaches.

Pattern-Based Diagnosis

Kotest — flexible, idiomatic Kotlin testing framework. Multiple specification styles (StringSpec, FunSpec, BehaviorSpec, DescribeSpec, FeatureSpec, FreeSpec), rich matcher library, property-based testing, data-driven tests, coroutine support, KMP-friendly. Drop-in alternative or complement to JUnit. USE WHEN: user mentions "Kotest", "io.kotest", "shouldBe", "StringSpec", "BehaviorSpec", "DescribeSpec", "kotest property testing", "Arb.list", "forAll", "kotest matchers", "kotlin tests" DO NOT USE FOR: JUnit-specific patterns - use junit skill (or framework-specific test skills) DO NOT USE FOR: Flow testing - use `testing/turbine` DO NOT USE FOR: Compose snapshot tests - use `testing/compose-snapshot` DO NOT USE FOR: Mobile E2E - use `testing/maestro`

Generates comprehensive unit tests with edge cases, error paths, and boundary values. Auto-detects the test framework, scans for untested functions, adopts existing conventions, runs tests, and self-heals failures in up to 3 iterations while measuring coverage.

Provides patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching in Nuxt 4 apps.

Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.

Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.

Guides writing idiomatic Rust with ownership, error handling, traits, concurrency, and best practices for safe, performant code.

Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.

Write effective unit tests with modern MSTest 3.x/4.x, covering assertion APIs, data-driven tests, and test lifecycle best practices.

Provides file paths to language-specific reference files for polyglot test analysis skills, enabling framework-aware detection of test markers, assertions, and patterns across .NET, Python, TypeScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++.

Diagnoses structural problems in an existing test suite—brittleness, mock overuse, and other decay risks—drawing on twelve classic engineering books including xUnit Test Patterns and Working Effectively with Legacy Code.

Write modern C# code with advanced features like records, pattern matching, and async/await. Optimizes .NET applications, implements enterprise patterns, and ensures comprehensive testing.