DocsWP — WordPress Help

Test Chat Summary: 29th January 2026

On January 29, 2026 15:00 GMT, <test-chat> started in #core-test facilitated by @ozgursar. The agenda can be found here.

1. Attendance

In attendance was:
@nikunj8866 @fakhriaz @sirlouen @ozgursar @wing.louie @huzaifaalmesbah @juanmaguitar @r1k0 @mosescursor @mebo (async) @mohkatz (async)

2. Volunteer

This week’s facilitator was @ozgursar

This week’s Note-taker was @ozgursar

3. Test Team Discussions

Proposal to archive old test reports

@sirlouen presented a proposal to archive old test reports that do not belong to the test team or are obsolete with the new structure. The goal is to move toward newer versions of the test reports structure.

Key GitHub issues requiring team review:

A proposed new version of the test reports plugin is being tested and is available at:

The team can test using WordPress Playground or download and install as a plugin to a local WordPress develop environment. @sirlouen aims to finalize the version before February and will send a PR once feedback is received. @nikunj8866 will also review and share feedback.

Officialize the two test reports

This was a major agenda item focused on making official decisions about test reports structure. Currently there are two official reports:

  1. Needs Reproduction (https://core.trac.wordpress.org/report/69)
    • Issues: Doesn’t have a good slug, filters the report weirdly (includes reporter-feedback, only accounts for bugs), not on homepage
  2. Patches Needing Testing (https://core.trac.wordpress.org/tickets/needs-testing)
    • Status: Has correct slug and is on homepage

Proposal discussed: Two alternatives were presented:

Option 1: Make needs-reproduction report official

  • Add it to homepage with a correct slug (/needs-reproduction)
  • Fix the filter parameters

Option 2: Unify into a single report that will include both Patch Testing and Needs Reproduction

Rationale for unification: Since anyone can add the needs-testing keyword to tickets, without solid principles on how to identify if a test needs reproduction or patch testing, confusion is inevitable. Testers need to do full analysis work regardless of keywords assigned to tickets, as the keywords cannot be reliably trusted.

Vote results: 5 to 1 in favor of having a single unified report

Next steps: Team members can comment on the handbook ticket until Monday. @sirlouen will send the final decision to meta.

4. Open Floor

WordCamp Asia 2026 Contributor Day

@nikunj8866 shared that @Krupa from the Contributor Day team reached out regarding Test Team Table Leads for WordCamp Asia 2026 Contributor Day.

Anyone attending WordCamp Asia 2026 in person and interested in leading the Test Team table should reply in the thread or reach out to @nikunj8866 directly. The handbook provides guidance on the role and responsibilities.

5. Announcements

6. Other Meetings

Props to @sirlouen, @mosescursor, @nikunj8866 for reviewing the post.

#core-test, #test-chat-summary