domains / families / software-engineering / test
Run Unity Test Runner operations asynchronously Run /test to write a test suite for code you just built or changed, after implementing a feature, route, or fix. Targets uncommitted changes automatically, reads test preferences.json for your framework (asks and saves it if absent), and picks the right strategy per file: happy path, edge cases, error states, accessibility.
The two skills share the name 'test' but perform completely different tasks. The first is a Unity-specific skill for running and managing Unity Test Runner jobs asynchronously via a specific API. The second is a general-purpose skill for writing test suites for uncommitted code changes in a repository, using git to determine scope and classifying files to choose testing strategies. They do not overlap in procedure, parameters, or domain logic.