What problem does it solve?
Scene-capture and pixel-based renderer tests can look reassuring while still being hollow, because they may pass even when the feature they are meant to verify is missing, broken, or being satisfied by unrelated pixels.
Core Features & Use Cases
- Mutation Verification: Temporarily remove or stub the render call for a feature and confirm the corresponding test fails.
- False-Positive Detection: Detect tests that are accidentally satisfied by backgrounds, HUD elements, anti-aliasing, or neighboring UI.
- Render Test Hardening: Tighten weak image assertions by narrowing regions, using feature-specific color predicates, and requiring meaningful pixel counts.
- Use Case: Before trusting a headless screenshot test for a game HUD, sprite, or chart, break the renderer once and verify the test goes red, then restore it and verify it goes green again.
Quick Start
Ask the skill to help you mutation-test a scene-capture assertion by stubbing the renderer for the feature under test and checking that the test fails and then passes again after restoration.