Triage & Testing

In context of testing incoming issues in bug repositories such as Trac or GitHub, triage means sorting and labeling incoming issues and testing means manually testing bug reports, questions, and feature requests. Triage is intended to be fast and to clear away clutter whereas testing is an unbiased look at the report and making sure it’s accurate and concise.

Triage Triage

  1. Label each issue with a focus area and type.
  2. Search right away for duplicate issues and close or consolidate them.
  3. Add any workflow labels such as Needs Testing.

Top ↑

Test Test

  1. Start with the Needs Testing or [Type] Bug label or the oldest issues.
  2. Search for duplicate issues and close or consolidate them.
  3. Make sure the title is accurate and descriptive.
  4. Check to make sure the issue is valid—if not, close the issue with a kind comment.
  5. Add steps to reproduce if they are missing.
  6. Add a screenshot if there isn’t already one and if it will add value.
  7. Ask clarifying questions if needed and add a label such as [Type] Needs More Info.

Top ↑

Details Details

  • 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.

When reviewing issues, try to remain as unbiased as possible. Follow the steps or explanation of the problem to the best of your ability and try to repeat it. State facts about what you tested and what happened. Stay concise, and only add a comment if you think it adds value.