The Test team patrols, curates, and tests the WordPress experience. We use a QA mindset to do visual records, using, observing, user research, manual testing, and user testing. We also document and triage top flows.
Triage & Testing Issues
Testing Bugs Testing Bugs
- Start with the
Needs Testing
or[Type] Bug
label or the oldest open issues.
Go toNeeds Technical Feedback
for issues that need testing from a developer perspective.
If you are testing from a support perspective,[Type] Help Request
is a good spot. - Always search for duplicate issues first and close or consolidate them with a thank you.
- Make sure the title is accurate and descriptive and suggest a change if it isn’t.
- Test to make sure the issue is valid—if not, suggest closing the issue with a kind comment.
- Add steps to reproduce if they are missing and would add value.
- Add a screenshot if there isn’t already one and if it will add value.
- Ask clarifying questions if needed and add a the
[Type] Needs More Info
label.
Triaging Incoming Issues Triaging Incoming Issues
- Start with the newest incoming issues or unlabeled open issues.
- Search right away for duplicate issues or issues that can be consolidated, and note them.
- If asking for more information would be helpful, ask right away.
- If the issue appears valid and urgent, test it right away.
- If you do not have rights to add labels, continue to the Testing Bugs section. If you do have rights to add labels, continue to the Triage for Admins section.
Triage for Admins Triage for Admins
In the case of GitHub, such as thegutenberg
repo, not everyone has write permissions to add labels or update titles. If you do have write permissions, you have the option to do a bit more in depth triage.
- Start with the newest incoming issues or unlabeled issues.
- Label each issue with a focus area and type.
- Update the title if it can be made more clear while still keeping it as short as possible.
- If the issue is a duplicate or can be consolidated, close it with a note and add the
[Status Duplicate
label. - If more information is needed, add the
[Status] Needs More Info
label and ask troubleshooting questions. - Add workflow labels if needed, such as
Needs Testing
,Needs Design Feedback
, orNeeds Decision
.
Good Details to Include Good Details to Include
- Add a screenshot whenever it makes sense. Videos should only be added if a screenshot isn’t enough to communicate the issue.
- Version numbers for WordPress, plugin (if applicable), OS, and browser.
- Errors from the browser Console tab in Developer Tools.
- Failed API calls from the browser Network tab in Developer Tools.
- Server error logs.