On Thursday, 12th February 2026 at 15:00 GMT, <test-chat> started in #core-test facilitated by @huzaifaalmesbah. The agenda can be found here.
1. Attendance
In attendance was: @ozgursar @mehrazmorshed @juanmaguitar @r1k0 @andrewssanya @mohkatz @noruzzaman @nikunj8866 (async)
2. Volunteer
This week’s facilitator was @huzaifaalmesbah
This week’s Note-taker was @huzaifaalmesbah
3. Test Team Discussions
Daily / Bi-Daily Testing Workflow Notice Proposal
@sajib1223 proposed adding a daily or bi-daily workflow notice to highlight tickets that need testing, include a quick-start guide, and possibly share weekly testing stats. The goal is to keep testing active, attract new contributors, and remind existing contributors.
@ozgursar asked how this would be automated. @huzaifaalmesbah suggested implementing it similar to the Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ “Needs Testing” announcer and later mentioned that he liked the idea and found it helpful.
@huzaifaalmesbah also suggested that @sajib1223 create a GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ issue in the Test Handbook repository so the broader Test Team can discuss and provide feedback.
@juanmaguitar proposed manually highlighting TRAC Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets with the needs-testing keyword, especially non-bug tickets in the 7.0 milestone that should be prioritized before the upcoming Beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 release.
Sync Weekly Meetings Section with the New Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Meeting Structure
The team discussed updating the Weekly Meetings section to align with the new Core Test meeting structure. @huzaifaalmesbah asked @mosescursor and @nikunj8866 to review the issue. @juanmaguitar offered to handle the update, mentioning that it only required editing page content.
@nikunj8866 confirmed that if JuanMa had the necessary access, he could proceed with updating the page. The update was completed by @juanmaguitar
Proposal – Restructure Test Handbook to Support Multiple Testing Domains
The team discussed the proposed project-based directory structure for the Test Handbook and next steps for implementation. Feedback was requested to help move the proposal forward.
@ozgursar shared that the new directory structure looks good and mentioned submitting a PR to add email testing instructions, which could fit into the new structure.
@juanmaguitar recommended avoiding duplicated information and instead linking to resources in other handbooks where possible.
@huzaifaalmesbah suggested first restructuring the Testing section under get-setup-for-testing, then placing email testing instructions in the most appropriate location.
The team agreed to continue the detailed discussion and feedback in the related GitHub issue before finalizing the structure and proceeding with updates.
4. Open Floor
During the Open Floor, @juanmaguitar highlighted a major feature planned for WordPress 7.0 the proposal to merge the WP AI Client into WordPress 7.0. He shared the related Trac ticket and noted that the post includes a “Call for Feedback and Testing,” encouraging contributors to review and provide feedback. He also reminded the team about the upcoming WP 7.0 Bug Scrub happening shortly after the meeting.
@huzaifaalmesbah thanked @juanmaguitar for surfacing the feature and asked about the WP Trac Triager Chrome extension created by @juanmaguitar — how it works and how it can support the Test Team.
@juanmaguitar explained that the extension enhances Trac ticket triage by surfacing key information in a clearer UI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing., including:
- The latest comments
- Milestone history
- Keyword explanations
- Component maintainers
- Keyword change history
- Quick links to comments
He shared that the tool is available on the Chrome Web Store and open to feedback via GitHub.
@ozgursar noted that the extension significantly improves Trac ticket triaging, especially for tickets with long discussion histories.
@huzaifaalmesbah added that the tool helps with quick navigation and makes it easier to identify reporters, committers, and maintainers at a glance. He expressed appreciation for the tool, highlighting that it helps the Test Team work more efficiently.
5. Announcements
WordPress Ecosystem Announcements
Test Team Announcements
Call for Testing
6. Other Meetings
Props to @bosskhj for reviewing this post
#core-test, #test-chat-summary
