QA Handoff Guide
Requirements and process for handing off development work for QA testing.
Handoff Requirements
Before requesting QA review, ensure all items are completed:
Code Requirements
- All features implemented per specifications
- Code reviewed (self or peer)
- No console errors or warnings
- Linting passes
- TypeScript compiles without errors
Environment Requirements
- Deployed to staging environment
- Staging reflects latest code
- Test data/accounts configured
- Third-party integrations working on staging
Documentation Requirements
- PR description complete
- Testing instructions provided
- Screenshots/videos for UI changes
- Edge cases documented
Handoff Checklist
Functionality Handoff
## Feature: [Feature Name]
### Implementation Summary
Brief description of what was implemented.
### Test Accounts
- Admin: admin@test.com / TestPass123
- User: user@test.com / TestPass123
### Test Data
- Sample products created: Product A, Product B
- Test discount code: TESTCODE
### Testing Instructions
1. Login as admin user
2. Navigate to /dashboard
3. Click "Create New"
4. Fill form with test data
5. Submit and verify success message
6. Verify data appears in list
### Expected Behavior
- Form validates required fields
- Success message appears on submit
- New item appears in list immediately
- Email notification sent (check staging inbox)
### Known Limitations
- Feature X not included in this phase
- Mobile optimization in separate ticket
### Edge Cases to Test
- Empty form submission
- Duplicate entries
- Special characters in text fields
- Very long text input
Bug Fix Handoff
## Bug Fix: [FLY-###] [Bug Title]
### Original Issue
Description of the bug and how to reproduce.
### Root Cause
What was causing the bug.
### Fix Applied
What was changed to fix it.
### Testing Instructions
1. Steps to verify bug is fixed
2. Additional steps
3. Expected result
### Regression Testing
- Related features to check: Feature A, Feature B
- No changes to: Feature C, Feature D
Environment Information
Staging URLs
| Environment | URL | Purpose |
|---|---|---|
| Staging | staging.clientsite.com | QA testing |
| Dev | dev.clientsite.com | Development testing |
| Production | clientsite.com | Live site |
Access Credentials
Store in project's 1Password vault:
- CMS admin credentials
- Test user accounts
- Third-party service logins
Communication
Handoff Message Template
@QA Team - Ready for testing
**Ticket**: [FLY-###] [Title]
**PR**: #123
**Staging**: staging.clientsite.com
**Summary**: [Brief description]
**Testing Focus**:
- Main feature flow
- Edge case X
- Mobile responsiveness
**Test Accounts**: See 1Password "Client - Test Accounts"
**Notes**: [Any special instructions]
QA Response Expected
- Acknowledgment: Within 4 hours
- Initial Testing: Within 24 hours
- Full Testing: Within 48 hours
Post-Handoff Process
Developer Responsibilities
- Stay Available: Be reachable for questions
- Monitor Feedback: Check for QA comments
- Fix Issues Quickly: Address blocking issues same day
- Update PR: Push fixes and notify QA
QA Feedback Loop
Developer QA Team
| |
|--- Handoff --->|
| |--- Testing
|<-- Questions --|
|--- Answers --->|
| |--- More Testing
|<-- Bug Report -|
|--- Fix ------->|
| |--- Verify Fix
|<-- Approved ---|
| |
Common Handoff Issues
Issue: Staging not updated
Solution: Always verify deployment before handoff
# Verify staging deployment
curl -I https://staging.clientsite.com | grep x-deployed-at
Issue: Missing test data
Solution: Include test data setup in handoff notes or provide seed script
Issue: Unclear testing scope
Solution: Always specify what IS and IS NOT included in the feature
Issue: Environment differences
Solution: Document any staging vs production differences
Pro Tip
Record a quick Loom video walking through the feature. It's faster than writing and clearer than screenshots.