domains / families / software-engineering / evidence-driven-testing

evidence-driven-testing

separate

Records visual proof while testing UI behavior — the agent tests the app hands-on via computer use while a screen recording with structured test/assertion annotations captures the session — then posts the video and a results summary to the requested destination. Use when changed runtime behavior needs observable verification, including headless environments (scripted screenshots and probes) and non-UI changes (measured numbers, output pairs).

When to use

• Testing UI behavior with visual proof
• Verifying changed runtime behavior
• Headless environment testing with scripted screenshots
• Non-UI changes verification with measured numbers
• Interactive flow testing via computer use
• CLI or API change verification with output pairs

When not to use

• Documentation-only edits
• Presenting synthetic pattern generators as UI evidence

Skill page

Source