What problem does it solve?
Adding a new public property, method, or event to a WinForms control requires a specific, repeatable set of unit tests, and missing categories like handle-state verification or event idempotency leads to incomplete coverage and CI failures.
Core Features & Use Cases
- Standardized Test Patterns: Provides naming conventions, the SubControl pattern for testing protected members, and data attributes like [WinFormsTheory] and [EnumData] for STA-thread-aware xUnit tests.
- Required Test Categories: Covers default values, set/get round-trips with and without a native handle, event firing and idempotency, OnXxx virtual method invocation, and ICommand binding lifecycles.
- CI Pitfall Guidance: Explains xUnit v3 analyzer rules such as passing CancellationToken to async calls and enabling #nullable context that fail CI builds.
- Use Case: When you add a new DialogResult-style property to a WinForms control, use this Skill to generate the full checklist of tests including handle-state assertions and event subscription/unsubscription verification.
Quick Start
Write the complete set of unit tests for a new public property on a WinForms control following the control-api-tests conventions.