Validation Checklist
Use this comprehensive checklist to confirm core platform functionality after deployments, updates, or when troubleshooting issues. Each check includes success criteria, common errors, and troubleshooting steps.5
Core System Checks5-10
Minutes to CompletePost-Deploy
Run After ChangesValidation Checks
Success Criteria
- ✓ Login page loads successfully
- ✓ Can log in with valid credentials
- ✓ Session persists after page refresh
- ✓ Token automatically refreshes before expiration
- ✓ Logout clears session completely
- ✓ No auth-related console errors
Common Errors
Troubleshooting Steps
- 1. Clear browser cache and localStorage
- 2. Check environment variables for auth keys
- 3. Verify OAuth redirect URIs are correct
- 4. Check network tab for failed auth requests
- 5. Ensure cookies are enabled in browser
Success Criteria
- ✓ Search page loads without errors
- ✓ Can enter address and submit search
- ✓ Results display OR meta code shown (NO_RESULTS, RATE_LIMITED)
- ✓ Property data includes expected fields (AVM, sqft, beds, baths)
- ✓ Source attribution shows "ATTOM" correctly
- ✓ Last updated timestamp is recent
Common Errors
Troubleshooting Steps
- 1. Check Settings → Integrations → ATTOM status
- 2. Verify ATTOM API keys are configured
- 3. Wait 5 minutes if rate limited
- 4. Try known working address (e.g., 123 Main St, San Francisco, CA)
- 5. Check API quota in ATTOM dashboard
Success Criteria
- ✓ Integrations page accessible from Settings
- ✓ All integration cards display
- ✓ Connection status shown for each integration
- ✓ Can click Connect/Disconnect buttons
- ✓ No console errors on page load
- ✓ Status updates reflect actual connection state
Common Errors
Troubleshooting Steps
- 1. Hard refresh page (Ctrl+Shift+R)
- 2. Check network tab for failed requests
- 3. Verify API endpoints are accessible
- 4. Reconnect each failing integration
- 5. Check browser console for specific errors
Success Criteria
- ✓ Sources page loads from navigation
- ✓ Existing sources display in list/table
- ✓ Can click "Add Source" button
- ✓ Form opens with all fields
- ✓ Can save new source successfully
- ✓ New source appears in list immediately
Common Errors
Troubleshooting Steps
- 1. Verify user role has data_source_create permission
- 2. Check feature gates for government_data
- 3. Ensure all required fields are completed
- 4. Check API response in network tab
- 5. Contact support if permissions issue
Success Criteria
- ✓ Notifications icon shows in header
- ✓ Unread count badge displays correctly
- ✓ Clicking icon opens notifications panel
- ✓ List loads without errors
- ✓ No duplicate notifications
- ✓ Count updates when marking as read
Common Errors
Troubleshooting Steps
- 1. Refresh page to clear cache
- 2. Check for single-flight caching in network tab
- 3. Verify WebSocket connection for real-time updates
- 4. Clear browser notifications and reload
- 5. Check console for fetch errors
How to Run Validation
Follow this systematic approach to validate your deployment:
- 1. PrepareOpen browser DevTools (F12). Clear cache with Ctrl+Shift+R. Have credentials ready.
- 2. Execute ChecksGo through each validation check systematically. Mark pass/fail for each.
- 3. Document FailuresScreenshot errors. Copy console logs. Note exact steps to reproduce.
- 4. Attempt FixesFollow troubleshooting steps for any failed checks. Re-test after each fix.
- 5. Report IssuesIf checks still fail after troubleshooting, escalate with documentation.
How to Capture Error Logs
When a validation check fails, proper error logging helps diagnose issues quickly:
Browser Console Logs
- 1. Press F12 to open DevTools
- 2. Go to Console tab
- 3. Right-click and 'Save as' to export
Network Requests
- 1. Open DevTools Network tab
- 2. Filter for failed requests (red)
- 3. Click request → Copy → Copy as cURL