Skip to main content
Tester: ___________________________ Start Date: ___________________________ Environment: the active QA deployment URL

Overall Progress


Day 1: Core Functionality (Wed)

Date: ___________________________ Hours Worked: ___________ Target: 10 tests Status Key: ⬜ Not Started | 🔄 In Progress | ✅ Pass | ❌ Fail | ⚠️ Blocked | ⏭️ Skip Day 1 Summary:
  • Tests Completed: ___ / 10
  • Pass Rate: ___%
  • Bugs Found: ___
  • Blockers: ___
Key Findings:
Questions for Dev Team:

Day 2: Advanced Features (Thu)

Date: ___________________________ Hours Worked: ___________ Target: 12 tests Day 2 Summary:
  • Tests Completed: ___ / 12
  • Pass Rate: ___%
  • Bugs Found: ___
  • Blockers: ___
Key Findings:
Questions for Dev Team:

Day 3: Edge Cases & Security (Fri)

Date: ___________________________ Hours Worked: ___________ Target: 18 tests Day 3 Summary:
  • Tests Completed: ___ / 18
  • Pass Rate: ___%
  • Bugs Found: ___
  • Blockers: ___
Key Findings:
Questions for Dev Team:

Bug Summary

Critical Bugs (Must Fix Before Production)

Block production deployment

High Priority Bugs (Should Fix Before Release)

Significant impact on functionality

Medium Priority Bugs

Should fix soon, but not blocking

Low Priority Bugs

Nice to have, cosmetic issues

Test Coverage by Feature Area


Risk Assessment

High Risk Areas

Features with critical bugs or failed tests

Medium Risk Areas

Features with some concerns

Production Readiness Checklist

Before recommending production deployment:

Critical Path (Must Pass)

  • Users can log in successfully
  • Admins can create forms
  • Forms can be published
  • Public users can submit forms
  • Admins can view submissions
  • No critical security vulnerabilities
  • File upload validation works
  • Access control prevents unauthorized access

Core Features (Should Work)

  • Email notifications send reliably
  • Form validation works correctly
  • Draft submissions save and restore
  • Portal applications workflow works
  • Team member permissions work
  • Mobile responsive design works
  • Form settings save correctly
  • Share links track responses

Nice to Have (Can Have Minor Issues)

  • Analytics display accurately
  • Webhooks deliver reliably
  • Integrations (Airtable, Plaid) work
  • Multi-language support works
  • Audit logs record all actions
  • Performance is acceptable

Final Recommendation

Production Ready? ⬜ Yes ⬜ No ⬜ Conditional Conditions (if conditional):
Rationale:
Top 3 Priorities:
  1. [Most critical item to address]
  2. [Second priority]
  3. [Third priority]
Testing Gaps:
Recommendations for Post-Launch:

Sign-Off

QA Tester: ___________________________ Signature: ___________________________ Date: ___________________________ Reviewed By: ___________________________ Signature: ___________________________ Date: ___________________________

Appendix: Test Environment Details

Testing Environment:
  • URL: [active QA deployment URL]
  • Branch: main
  • Last Deploy: ___________________________
  • Commit Hash: ___________________________
Test Accounts Used:
  • Admin: ___________________________
  • User: ___________________________
  • Additional: ___________________________
Browsers Tested:
  • Chrome _____ (version)
  • Firefox _____ (version)
  • Safari _____ (version)
  • Edge _____ (version)
Devices Tested:
  • Desktop (macOS/Windows/Linux)
  • Mobile (iOS/Android)
  • Tablet
Third-Party Tools:
  • webhook.site (for webhook testing)
  • Airtable (if applicable)
  • Plaid Sandbox (if applicable)

Notes Section

Use this space for general notes, observations, or additional context