Officialize the Test Reports

[SirLouen]

Following with the updates in the reports: #99

It's time to officialize the two reports into Core reports:

Needs Reproduction

This report is not listed in the tickets section: https://make.wordpress.org/core/reports/

This is the report: https://core.trac.wordpress.org/report/69
It doesn't have a slug also. A slug like /needs-reproduction would be good

Current SQL Query

-- ## 69: Bugs that Needs Reproduction (in progress) ## --

-- {{{
-- #!span class="create-new-ticket button button-large button-primary"
-- [https://login.wordpress.org/?redirect_to=https://core.trac.wordpress.org/newticket Create a new ticket]
-- }}}
--  * Tickets that are bugs and
--    * Need feedback from whoever reported the ticket, usually because we're failing to reproduce (keyword: reporter-feedback)
--    * Don't have a patch, don't need a patch, and need testing

SELECT
  id AS ticket,
  summary,
  CASE
  WHEN status = 'accepted'
  THEN owner || '*'
  WHEN owner <> 'anonymous'
  THEN owner
  ELSE ''
  END as owner,
  component as __group__,
  keywords,
  version as _version,
  priority as priority,
  severity,
  milestone as milestone,
  t.type AS type,
  status AS _status,
  time AS _created,
  changetime AS modified,
  description AS _description,
  reporter AS _reporter
FROM ticket t
WHERE status <> 'closed' 
  AND type == 'defect (bug)'
  AND Component <> 'WordPress.org'
  AND ( 
    keywords LIKE '%reporter_feedback%'
    OR ( keywords LIKE '%needs_testing%' AND keywords NOT LIKE '%needs_patch%' AND keywords NOT LIKE '%has_patch%' ) 
  )
ORDER BY
  milestone <= ( SELECT min(name) FROM milestone WHERE completed = 0 AND name NOT LIKE '%.%.%' ) DESC,
  Component, t.type, summary

Patches Needing testing

Report: https://core.trac.wordpress.org/tickets/needs-testing

Current SQL Query:

-- ## 15: Has Patch and Needs Testing ## --

-- {{{
-- #!span class="create-new-ticket button button-large button-primary"
-- [https://login.wordpress.org/?redirect_to=https://core.trac.wordpress.org/newticket Create a new ticket]
-- }}}
-- 
--  * Tickets that have a patch and are explicitly marked as needing extra testing
--  * Sorted by component, type, summary
--  * Accepted tickets have an '*' appended to their owner's name

SELECT
  CASE
  WHEN milestone <= ( SELECT min(name) FROM milestone WHERE completed = 0 AND name NOT LIKE '%.%.%' )
  THEN 'Next Release'
  ELSE 'Future Releases'
  END as __group__,
  id AS ticket,
  summary,
  CASE
  WHEN status = 'accepted'
  THEN owner || '*'
  WHEN owner <> 'anonymous'
  THEN owner
  ELSE ''
  END as owner,
  component,
  version as _version,
  priority as priority,
  severity,
  milestone as milestone,
  t.type AS type,
  status AS _status,
  CASE
  WHEN keywords LIKE '%needs_unit_tests%'
  THEN 'needs-unit-tests'
  WHEN keywords LIKE '%needs_docs%'
  THEN 'needs-docs'
  WHEN keywords LIKE '%changes_requested%'
  THEN 'changes-requested'
  WHEN keywords LIKE '%close%'
  THEN 'close'
  WHEN keywords LIKE '%needs_review%'
  THEN 'needs-review'
  WHEN keywords LIKE '%dev_feedback%' OR keywords LIKE '%2nd_opinion%'
  THEN 'dev-feedback'
  WHEN keywords LIKE '%reporter_feedback%'
  THEN 'reporter-feedback'
  WHEN keywords LIKE '%commit%'
  THEN 'commit'
  WHEN keywords LIKE '%tested%'
  THEN 'tested'
  WHEN keywords LIKE '%has_patch%'
    OR keywords LIKE '%needs_testing%' AND keywords NOT LIKE '%needs_patch%'
  THEN 'has-patch'
  WHEN keywords LIKE '%early%'
  THEN 'early'
  ELSE ''
  END as workflow,
  time AS _created,
  changetime AS modified,
  description AS _description,
  reporter AS _reporter
FROM ticket t
WHERE status <> 'closed' 
  AND Component <> 'WordPress.org'
  AND keywords LIKE '%needs_testing%'
  AND keywords LIKE '%has_patch%'
ORDER BY
  milestone <= ( SELECT min(name) FROM milestone WHERE completed = 0 AND name NOT LIKE '%.%.%' ) DESC,
  Component, t.type, summary

[SirLouen]

For the needs reproduction:

There are keywords that should be removed:
keywords LIKE '%reporter_feedback%'
keywords NOT LIKE '%needs_patch%'
And type AND type == 'defect (bug)'
Currently there are 205 tickets here.
Also the problem here is that pretty much anyone can set the needs-testing. So technically, not all reports really need a reproduction report, as many has been set with needs-testing as a staple.

For the needs testing:
It depends what purpose this report is seeking
For testers, any report without a Milestone (Future Release or slated a specific milestone), should not be displayed.
But for the general testing team, pretty much all reports should be triaged and cleared at some point.
Currently there are 291 tickets here

In total there are 496 reports with needs-testing

Personally I believe, that those reports should be useful for upcoming members. We are trying to define our reports in make.wordpress.org/test and make.wordpress.org/updates, so basically the reports in all areas remain consistent.

[SirLouen]

I would like to officialize these two reports in the next meeting 29th january 2026 and pass them to meta to be updated.