contract-testing-dotnet

Generate and run contract tests for .NET services with Microcks validation.

8|2|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill contract-testing-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contract-testing-dotnet
Source: https://github.com/SebastienDegodez/skraft-plugin/tree/main/plugins/skills/contract-testing-dotnet
Command: npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill contract-testing-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Microcks.Testcontainers, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates contract testing for .NET services, ensuring that API providers adhere to the published contracts without manual oversight.

Core Features & Use Cases

  • Baseline Contract Testing: Provides a standard set of integration tests with WebApplicationFactory and typed HttpClient.
  • Microcks Integration: Optionally extends testing with Microcks to validate against the published contract, ensuring service conformance.
  • Use Case: After deploying a new .NET service, use this Skill to automate the contract tests and validate the API against the specified contract.

Quick Start

To initiate contract testing, run the 'dotnet test' command after configuring the contract testing Skill.

Frequently Asked Questions about contract-testing-dotnet

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

FAQPage Schema
How do I automate contract testing for .NET services?

Automating contract testing for .NET services is achieved by generating test cases from API contracts and running them via the 'dotnet test' command after configuring the testing environment.

What is contract testing and how does Microcks validate API conformance?

Contract testing verifies that API providers adhere to published contracts, and Microcks optionally extends this by validating your .NET service responses directly against the specified API contract.

Do I need Microcks to run integration tests with WebApplicationFactory?

You do not need Microcks for baseline contract testing, which uses a standard set of integration tests with WebApplicationFactory and a typed HttpClient, but it is required for optional contract validation.

Can I use this Skill to validate a newly deployed .NET API against a contract?

Yes, after deploying a new .NET service, you can use this Skill to automate contract tests and validate the API against the specified contract to ensure service conformance.

What are the limitations of using Microcks.Testcontainers for .NET API testing?

The primary limitation is that this Skill requires a .NET environment, and utilizing the optional Microcks validation for additional verification depends on the Microcks.Testcontainers dependency.