What problem does it solve? Writing unit tests for Thinkwise Software Factory control procedures requires deep knowledge of the unit_test entity model, its child entities, mock data sets, and connector quirks. This Skill guides the full lifecycle so tests are grounded in the actual generated code, approved by the user before any model writes, and correctly built and executed through the MCP connector. ## Core Features & Use Cases - Three-phase workflow: Propose a scenario list grounded in the target control procedure's real branches, get explicit user sign-off, then build the unit_test rows and child entities via the staging flow. - Full entity coverage: Handles all test types (DEFAULT, LAYOUT, CONTEXT, BADGE, TASK, PROCESS, SUBROUTINE, HANDLE_, TRIGGER_) with confirmed-live guidance on entities, enums, tasks, and known connector pitfalls. - Mock data authoring: Step-by-step recipe for building data_set mock rows through the API, including FK-chain mocking, explicit identity values, and permission troubleshooting. - Use Case: A developer asks for test coverage on a new default procedure. The Skill reads the generated code, proposes scenarios like boundary and sad-path cases, gets approval, then creates the unit_test via task_copy_unit_test, adds input/output rows, links mock data, and runs the test to confirm it passes. ## Quick Start Ask the assistant to suggest and create unit tests for a specific control procedure in your Software Factory model, and it will propose scenarios for your approval before building anything.
