Test Software Behavior

Run this workflow only when the user explicitly invokes this skill by name. A related keyword or an ordinary implementation request is not an invocation.

Identify the intended contract, supported environments, and observable failure. Read existing tests and test configuration before adding tools. Current output, visible fixtures, and implementation details are evidence, not automatically the specification. Resolve material uncertainty instead of blessing it with a test.

Choose the smallest combination of test boundaries that can distinguish a real incorrect implementation. Do not replace a required integration, host, or install check with compilation or a mocked unit test. Reuse the project's runner and fixtures; add a maintained test tool only when it supplies a needed capability.