tests

Write and maintain C# unit, integration, and validator tests with Arrange/Act/Assert structure.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill tests-sergeumatyasov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tests
Source: https://github.com/SergeuMatyasov/dotnet-shared-skills/tree/main/unit-testing
Command: npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill tests-sergeumatyasov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Этот навык помогает писать и поддерживать автоматизированные тесты в проектах на C#, делая их понятными и надёжными.

Core Features & Use Cases

  • Подсказки по структуре тестов (Arrange/Act/Assert), единообразное именование.
  • Правила по формированию и обновлению тестов: позитивные, негативные и граничные сценарии.
  • Гарантии детерминированности тестов и изоляции от внешних зависимостей.

Quick Start

Create a new test following the Arrange/Act/Assert pattern, include a Russian summary above the method, and name it using the Method_ShouldResult_WhenCondition convention.

Frequently Asked Questions about tests

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

FAQPage Schema
How do I write readable and reliable unit tests in C#?

To write reliable C# unit tests, structure tests using the Arrange/Act/Assert pattern, add a Russian summary above the method, and name them using the Method_ShouldResult_WhenCondition convention for clarity.

What is the best way to organize integration tests for .NET projects?

The best way to organize .NET integration tests is by enforcing determinism, isolating from external dependencies through safe mocking practices, and maintaining proper test organization with consistent naming conventions.

How do I ensure deterministic behavior when writing C# automated tests?

You ensure deterministic behavior in C# automated tests by isolating them from external dependencies using safe mocking practices, which guarantees tests run reliably under the same conditions every time.

Does this approach support creating both positive and negative test scenarios in .NET?

Yes, this approach supports creating and updating positive, negative, and boundary test scenarios in .NET, ensuring comprehensive coverage and consistent structure across all automated validator tests.

Why do my C# tests fail intermittently and lack proper isolation?

C# tests fail intermittently and lack proper isolation when they are not fully detached from external dependencies, which is resolved by enforcing safe mocking practices and deterministic behavior.