test-helpers

To generate test helpers for Unity C# projects, run the scaffold command to create the base library, then generate system-specific helpers. This automates factory functions, mock objects, and assertion utilities while conforming to existing project conventions without overwriting files.

Engine-specific test helpers are reusable utilities for assertions, object creation, and setup patterns tailored to your engine and language. You need them when expanding test suites where common setup and mock object creation patterns recur across multiple systems.

Yes, automated test helper generation reads SKILL metadata and optional system prompts to conform to project conventions. It outputs new helpers under tests/helpers/ that mirror existing style and deliberately avoids overwriting any existing files in your test suite.

The best way to scaffold assertion utilities and mock objects for Unity testing is running a two-step generation process: first scaffold the base library, then generate per-system helpers tailored to your project's current engine, language, and test patterns.

No, generating test helpers will not overwrite existing files. The process creates new helpers under tests/helpers/ that mirror your existing style, ensuring current factory functions, mock objects, and assertion utilities remain intact while standardizing new patterns.

Yes, you can create per-system test helpers for specific Unity components and C# scripts. After scaffolding the base library, generate system-specific helpers that provide tailored assertion utilities and factory functions based on your project's current engine and test patterns.