QA & Testing

Test plans, quality assurance practices, and testing documentation

This section contains quality assurance documentation, test plans, and testing practices for Morphir .NET.

Test Plans

Document	Description
Phase 1 Test Plan	Initial test plan for Phase 1 features
Copilot Skill Emulation Test Plan	BDD scenarios for GitHub Copilot skill emulation

Test Reports

Document	Description
Copilot Skill Emulation Execution Report	Results from skill emulation testing
Copilot Scenarios Runner	Automated scenario execution documentation

Internal tools

Document	Description
WASM host qualification	The internal, experimental `mck wasm-host` commands

Testing Practices

Test-Driven Development (TDD)

All development in morphir-dotnet follows TDD:

RED: Write a failing test first
GREEN: Write minimal code to pass the test
REFACTOR: Improve code while keeping tests green

Test Types

Type	Framework	Purpose
Unit Tests	TUnit	Individual component testing
BDD Tests	Reqnroll	Behavior specification and acceptance
Property Tests	FsCheck	Property-based verification
Integration Tests	TUnit	Cross-component integration

Test Isolation

Tests run in parallel and must not touch the developer’s machine. Run child processes through TestSandbox and ChildProcess, clean up with TolerantDirectory, and add the machine tripwire to process-heavy test projects. See Test Isolation.

Coverage Requirements

Minimum Coverage: 80% for all new code
Critical Paths: 100% coverage for IR handling, validation, and CLI commands
Regression Prevention: All bug fixes require accompanying tests

Running Tests

# Run all tests
dotnet test --nologo

# Run with coverage
dotnet test --collect:"XPlat Code Coverage"

# Run specific test project
dotnet test tests/Morphir.Core.Tests