Opened 11 months ago

Last modified 11 months ago

#5634 new enhancement

Introduce a 'needs-testing-info' Workflow keyword

Reported by: davidbaumwald Owned by:
Milestone: Priority: normal
Component: Trac Keywords: needs-copy-review


During the course of WP 5.6 and 5.7, a new custom workflow keyword has been used to request a more documented, patch validation procedure. In the same vein as #4609, this was discussed during Dev Chat on 2/24/21, and there was some agreement on including this in the official list.

As for a definition for needs-testing-info, it could start with...
"Contributors have requested a more detailed testing procedure to validate patch efficacy."

Flagging for a copy review to improve the definition.

Change History (4)

This ticket was mentioned in Slack in #core by david.baumwald. View the logs.

11 months ago

This ticket was mentioned in Slack in #core by david.baumwald. View the logs.

11 months ago

#3 @hellofromTonya
11 months ago

During 5.6 and 5.7, used needs-testing-info to request needed information for contributors to do manual testing.

Questions asked when applying the keyword:

  • What are the steps to reproduce? (i.e. for defects)
  • What are the steps to test?
  • Are there any testing dependencies, such as a plugin or script?
  • What is the expected behavior after applying the patch?

The answers to these questions help testers whether doing manual testing or creating unit tests.

Why this keyword?

  • Tickets are tagged with needs-testing. However, this keyword does not indicate if the ticket is in a state to be tested. Adding needs-testing-info alerts triage, ticket owner, maintainers, and testing team that this ticket needs more information and is not yet ready for testing.
  • It also creates a workflow for triage and testing follow-up in order to move the ticket closer to resolution.

#4 @hellofromTonya
11 months ago


In addition to needs-testing-info, I propose adding has-testing-info keyword.


needs-testing keyword by itself does not indicate the ticket's patch is ready for testing. Rather, it's a flag to know that the ticket will require testing when it's ready.

Adding needs-testing-info keyword flags more information is needed to know how to reproduce and do the testing as well as what the acceptable state/criteria are (ie expected behavior and acceptance criteria). This keyword is applied manually. The absence of this keyword does not indicate the ticket is in a testable state.

Adding has-testing-info is a positive indicator. The combination of needs-testing + has-testing-info creates a ready for testing workflow. Now the ticket can be scheduled in a testing scrub and/or a call for testers.

Note: See TracTickets for help on using tickets.