Mephistic
commented
2 months ago After talking with Matt, here are the key points he looks for before a deployment:
- Key point is the Testimony Flow (This seems like a high value first test)
- Submit a Testimony (should only be done on DEV to avoid polluting production data)
- Check that the email client should open at the end (we don't send the email ourselves - this is likely just making sure the email link is populated and clicked)
- Check that the copyable text is copying (should include the legislator addresses for email, and the testimony itself for the email body)
- Next up is that the 11 Main Site Pages load (E.g. Home Page, Learn Pages, About Pages)
- Browse Bills Page
- Bill Search + Filtering should work
- Should be able to navigate to a Bill Detail page
- Browse Testimony Page
- Testimony Search + Filtering should work
- Should be able to navigate to a Testimony Detail page
- Admin Page
- Admin page should load
@mvictor55 Let me know if I missed anything or anything else comes to mind
Summary
In order to build confidence around deploys, we should write up a manual QA checklist that lists the parts of the site we would need to confirm work as expected in order to feel comfortable saying a deployment is healthy.
Features to test might include e.g. Home Page, Login, View Bills, Search, View Testimony, Submit Testimony, etc.
This plan will eventually serve as a roadmap for prioritizing E2E tests to automate this process.
Success Criteria: