On 13 August 2025 at 4PM GMT, <test-chat> started in #core-test facilitated by @sirlouen The agenda can be found here.
1. Attendance
@oglekler @nikunj8866 @agulbra @callumbw95 and @getsyash
2. Volunteer
This week’s Note-taker was @sirlouen
3. Announcements
4. Test Team Updates
5. Focal Group Updates
6. Calls for Testers/Visibility
@agulbra, the main contributor to WordPress Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket #31992 on “Unicode email addresses”, has largely completed the development work but has been testing it himself, which is not ideal. @SirLouen emphasizes the need for independent testing and suggests that @agulbra prepare clear, detailed test cases so both technical and non-technical testers can contribute, aiming for at least three to four independent reports. Potentially during the next Patch Testing Triage next 18 August 2025 at 1.30PM GMT.
7. Test Team Discussion, Questions, and Blockers
Proposal to review the official Test Reports in Trac
The main topic is the proposal to review official Trac Test Reports related to the WordPress Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. test team activities. @oglekler and @sirlouen discuss the existence and visibility of three main reports: Needs Testing, Needs Unit Tests and Needs Reproduction (with the last one being less accessible and considered inaccurate).
The proposal is to create specific queries for each report and holding a vote in one of the next official test team meeting to decide which queries should be accepted. The results would then be forwarded to the Core administration team for potential changes, as these reports directly affect the Test Team’s activities.
The overall idea is to formalize the process of selecting and refining these reports through the test team’s official meetings and votes. This process would help maintain effective tracking of testing tasks by having official and accurate reports that reflect the test team’s needs and priorities.
8. Open Floor
No additional topics were brought during the open floor section of the meeting.
9. Next Test Team Sessions
Props to @krupajnanda and @oglekler helping review these notes and offering feedback.
#core-test
