Nikunj Hatkar 3:34 pm on September 12, 2025
Tags:   

Test Chat Summary: September 10th, 2025

On Wednesday, 10 September 2025, 04:00 PM UTC, <test-chat> started in  #core-test facilitated by @nikunj8866. The agenda can be found here.

1. Attendance

@nikunj8866 @oglekler @krupajnanda @dilip2615 @pmbaldha @doreen233 @sirlouen

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Announcements

4. Test Team Updates

5. Focal Group Updates

@sirlouen mentioned that Contributors Onboarding & Coffee Hours session will be replaced with Patch Testing Scrubs, held after the weekly #core Live Bug Scrubs (Thursdays @ 1PM GMT).

6. Calls for Testers

Here are some tickets that need testing. This is a call for community testers to take them up whenever possible.

7. Test Team Discussion, Questions, and Blockers

7.1 Tested Keyword Proposal

  • @oglekler suggested introducing tested a keyword in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. so contributors can explicitly sign off with their name after testing a patch. This would add accountability and clarity to the testing process.

7.2 Current State of Testing

  • @sirlouen noted that testing is still happening somewhat at random, though it has improved compared to last year. He also pointed out there is no consistent or official testing protocol in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • @oglekler agreed, saying that currently contributors just “rummage around” to find something to test.

7.3 Quality Assurance vs. Testing

  • @oglekler highlighted that the conversation should focus on Quality Assurance, not just testing. In commercial development, releases do not go live without QA approval, and this should become a WordPress standard.

7.4 Double-Test Enforcement

  • @sirlouen proposed enforcing a minimum of two independent tests before committing a patch, similar to the double sign-off required for RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. backports. He also admitted this may not be feasible right now due to limited testing resources.

7.5 Test Scrubs & Releases

  • @sirlouen suggested Test Scrubs could run side-by-side with bug scrubs during releases.
  • @krupajnanda explained that during release cycles, triage is often converted into a test scrub by targeting tickets scheduled for the upcoming version.
  • @sirlouen stressed that enforcing a “two-test” policy would make tickets nearly ready to commit once they are milestoned.

@sirlouen proposed the following actions:

  • Update the weekly report to include solicited tests.
  • Maintain a clear queue of requested tests (via Trac reports or another tool).
  • Keep the queue short with support from ongoing scrubs.

8. Open Floor

No additional topics were brought up during the open floor section of the meeting.

9. Next Test Team Sessions

Props to @krupajnanda and @sirlouen for helping review these notes and offering feedback.

#core-test