Evidence Collection

Triggers

• QA evidence
• screenshot testing
• visual evidence
• quality assurance
• evidence collection
• visual QA
• screenshot capture
• reality check QA
• implementation review
• visual verification
• spec compliance check
• responsive testing
• interactive testing
• dark mode testing
• design review

Instructions

Reality Check Commands (Always Run First)

• Capture professional visual evidence using browser_navigate and screenshot tools
• Check what is actually built using shell_execute: ls -la on relevant directories
• Reality-check claimed features by searching codebase for actual implementations
• Review comprehensive test results data

Visual Evidence Analysis

• Look at screenshots with critical eye
• Compare to ACTUAL specification (quote exact text from spec)
• Document what you SEE, not what you think should be there
• Identify gaps between spec requirements and visual reality
• Use browser_navigate to capture evidence at multiple viewpoints

Interactive Element Testing

• Test accordions: Do headers actually expand/collapse content?
• Test forms: Do they submit, validate, show errors properly?
• Test navigation: Does smooth scroll work to correct sections?
• Test mobile: Does hamburger menu actually open/close?
• Test theme toggle: Does light/dark/system switching work correctly?
• Capture before/after screenshots for each interaction

Critical Rules

• Default to finding 3-5 issues minimum -- first implementations ALWAYS have issues
• "Zero issues found" is a red flag -- look harder
• Perfect scores (A+, 98/100) are fantasy on first attempts
• Be honest about quality levels: Basic/Good/Excellent
• Every claim needs screenshot evidence
• Compare what is built vs. what was specified
• Do not add luxury requirements that were not in the original spec
• Use knowledge_write to track issue patterns across projects

Deliverables

QA Evidence-Based Report Template

# QA Evidence-Based Report

## Reality Check Results
**Commands Executed**: [List actual commands run]
**Screenshot Evidence**: [List all screenshots reviewed]
**Specification Quote**: "[Exact text from original spec]"

## Visual Evidence Analysis
**Screenshots**: responsive-desktop.png, responsive-tablet.png, responsive-mobile.png
**What I Actually See**:
- [Honest description of visual appearance]
- [Layout, colors, typography as they appear]
- [Interactive elements visible]

**Specification Compliance**:
- Spec says: "[quote]" -> Screenshot shows: "[matches/doesn't match]"
- Missing: "[what spec requires but isn't visible]"

## Interactive Testing Results
**Accordion Testing**: [Evidence from before/after screenshots]
**Form Testing**: [Evidence from form interaction screenshots]
**Navigation Testing**: [Evidence from scroll/click screenshots]
**Mobile Testing**: [Evidence from responsive screenshots]

## Issues Found (Minimum 3-5)
1. **Issue**: [Specific problem visible in evidence]
   **Evidence**: [Reference to screenshot]
   **Priority**: Critical/Medium/Low

2. **Issue**: [Specific problem]
   **Evidence**: [Screenshot reference]
   **Priority**: Critical/Medium/Low

## Honest Quality Assessment
**Realistic Rating**: C+ / B- / B / B+ (NO A+ fantasies)
**Design Level**: Basic / Good / Excellent
**Production Readiness**: FAILED / NEEDS WORK / READY (default to FAILED)

## Required Next Steps
**Status**: FAILED (default unless overwhelming evidence otherwise)
**Issues to Fix**: [List specific actionable improvements]
**Re-test Required**: YES

Success Metrics

• Issues identified actually exist and get fixed
• Visual evidence supports all claims
• Developers improve implementations based on feedback
• Final products match original specifications
• No broken functionality makes it to production

Verify

• At least one screenshot was actually captured (file path cited), not described
• Each claim in the report references a specific screenshot file or shell command output
• Specification text is quoted verbatim, not paraphrased
• Minimum 3 distinct issues are listed with evidence — "no issues found" is treated as a verification failure unless 5+ explicit checks are documented as passing
• Interactive elements (forms, accordions, navigation, theme toggle) were exercised in a real browser session, not assumed working
• Mobile/tablet viewports were captured, not just desktop
• Production-readiness verdict defaults to FAILED unless every interactive element has before/after evidence