Note: This page is a guide for TAMs on how to initiate the QA process. Engineers should use our QA Checklist and Performance Guidelines page in our Developer Handbook for the checklist and details of performing QA (███████████████).
Please see this page for details of Design QA.
When initiating QA, make sure you have everything ready and gathered before pinging our QA Engineer.
Step 1: Adding access for our QA Engineer
Usernames can be found in our Contractor Onboarding doc (███████████████). ███████████████
- Add them to the project’s GitHub repo with ‘write’ access
- Add them to
/wp-admin– add them directly, no need to share any 1Pass access- SafetyNet does now allow password reset emails to go through. No need to send the contractor passwords via QuickForget.com.
Step 2: Communicate
Ping our QA engineer in ███████████████ with the following information:
- Is design approved?
- Has design shifted?
- Is there anything they should focus on during QA?
- Link to site for testing
- Which developer is currently assigned to the project
Add a comment on the project P2 with these details as well.
Here is a handy predef that outlines what should be included in the engineer ping:
Request for Functional QA
Hello [@-mention QA Engineer]!
We have a new project that’s ready for QA. We should aim to have the QA completed by [due date], please let us know if that timeline is feasible.
QA details
URL: [Site URL to be checked]
Figma: [Link to Figma file]
GitHub: [Link to GitHub repo]
Should the site be compared to Figma: [Yes/No/Comment]
Who should the QA issues be assigned to: [TAM/dev – include GH username]Other important things to note
[Add other relevant information about the project, example below]
Below you’ll find a list of open issues we are working on, so if your testing surfaces any of these issues, feel free to move on:
CC: [@-mention pair TAMs or other relevant stakeholders]
Automattic Special Projects 