Tonya Mork 4:18 pm on May 3, 2021
Tags:   

Bi-Weekly Test Team Triage Meetings

Last week, the Test Team agreed to do bi-weekly test triage sessions. These meetings will happen every other Tuesday at 13:00 UTC (starting this week).

Next test triage meeting will be held on 2021-05-04 13:00 in the #core-test on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Come join to triage with the team.

The meetings are now in the calendar.

What is triage for the Test Team?

In context of bug repositories such as TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. or GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, triage means sorting, labeling, and closing duplicate incoming issues and testing means manually testing bug reports, questions, and feature requests.

Triage & Testing Issues in Test Team’s handbook

The goals are:

  • to evaluate where each ticket is in its lifecycle and what the next step is to get it closer to a testable state
  • when in a testable state, to validate the patch/PR works as expected and, if applicable, provide feedback on the experience

When is a ticket in a testable state?

There are multiple “testable” states in a ticket’s lifecycle including these (keyword shown in parentheses):

  • Ready to reproduce the reported issue
  • Ready to manual test the patch
    • State:
      • has a patch (has-patch)
      • is marked for testing (needs-testing)
      • has “how to reproduce” instructions, if defect ticket
      • has “how to test” the patch instructions (has-testing-info)
    • Trac reports: with all the above states || without the testing info
  • Ready to build the automated tests
    • State:
      • has a patch (has-patch)
      • does not have automated tests (needs-unit-tests)
      • has “how to reproduce” instructions, if defect ticket
      • has “how to test” the patch instructions (has-testing-info)
    • Trac reports: with all the above states | without the testing info

Props to @francina for peer review.