Nikunj Hatkar 5:01 am on April 21, 2026
Tags: , ,   

Test Chat Summary: April 16th, 2026

On Thursday, 16 April 2026, 03:00 PM UTC, <test-chat> started in  #core-test facilitated by @nikunj8866. The agenda can be found here.

1. Attendance

In attendance was:
@ozgursar @nikunj8866 @juanmaguitar @mosescursor @huzaifaalmesbah @r1k0 @khushdoms (async) @mohkatz (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

Review the current handbook PRs before publishing

  1. Add Team Organization page with active and emeritus member sections
    • The team discussed the progress of the handbook PR proposing a new Team Organization page, including sections for Active Members and Emeritus Members.
    • @ozgursar mentioned that maintaining an Active Members list could be difficult and may quickly become outdated. @juanmaguitar agreed with this concern and noted that similar lists in other teams are often hard to maintain.
    • @nikunj8866 suggested defining Active Members based on contributions over the last 2–3 months, including meeting participation, testing, and feedback. He also proposed reviewing the list periodically to keep it accurate.
    • Further discussion led to a preference for focusing on an Emeritus Members list instead. @ozgursar suggested that having only an Emeritus list would be easier to maintain.
    • @nikunj8866 added that past Team Reps could be included in the Emeritus list, recognizing their contributions.
    • The team agreed to continue the discussion in the PR comments to finalize the approach.
  2. Archive old test report pages (testing-instructions, combined-report)
    • The team reviewed the PR aimed at archiving outdated test report pages such as testing instructions and combined reports.
    • @ozgursar noted that the Test Reports pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. should be referenced, as it was not clearly visible in the updated content. @juanmaguitar clarified that the PR is focused on deprecating old content and keeping only essential references in the handbook, suggesting that additional improvements should be handled in separate issues.
    • @nikunj8866 agreed with this approach and suggested creating a new issue to address the plugin reference. The team agreed that the PR is in good shape and ready for final review and merge after the meeting.
  3. Add cross-links between setup guides and patch testing report page
    • The team discussed a PR focused on improving cross-linking between setup guides and patch testing report pages.
    • @juanmaguitar noted that there are currently no clear instructions or templates for test reports in GutenbergGutenberg 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/, only references to patch testing. @nikunj8866 pointed out that there is already an open issue to address this gap and suggested continuing the discussion there.
    • The team agreed that additional issues should be created to define proper guidance for test reports and improve documentation clarity.

Proposed new handbook pages

  1. Create Test (or Test Team) in WordPress GitHub Teams
    • The team discussed a proposal to create a dedicated Test Team group within the WordPress GitHubGitHub 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/ organization.
    • @juanmaguitar explained that GitHub teams can help organize contributors, making it easier to tag specific groups for testing or triage. @ozgursar compared it to a role-based grouping system.
    • @nikunj8866 raised a question about whether other Make WordPress teams are using similar setups. During the discussion, it was noted that contributors need to be part of the WordPress GitHub organization to be added to such teams.
    • @juanmaguitar created an initial team but was unable to add members due to permission limitations. The team agreed to follow up in the #meta channel to clarify how contributors can be added to the organization.

4. Open Floor

  • @mosescursor questioned whether frequent meetings might be contributing to lower attendance. @juanmaguitar noted that weekly meetings are common across other Make WordPress teams.
  • @nikunj8866 suggested returning to a more focused schedule by alternating meetings:
    • One week for patch testing scrubs
    • One week for Test Team chats
  • @juanmaguitar agreed with this approach, and the team supported the idea. @nikunj8866 created a GitHub issue #154 to continue the discussion and finalize the plan.
  • @nikunj8866 shared a call for volunteers for Table Lead and Co-Lead roles for Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 2026. Contributors interested in participating or nominating others were encouraged to apply via the provided form.

5. Announcements

WordPress Ecosystem Announcements

  1. WordPress Core Dev Environment Toolkit: A Faster Path to Your First Core Contribution
  2. Twenty Twenty-Seven: Team Announcement
  3. Defining expectations for Iteration issues
  4. What’s new in Gutenberg 22.9? (8 April)
  5. Elevating Individuals
  6. What’s new for developers? (April 2026)
  7. @wordpress/build, the next generation of WordPress plugin build tooling

Test Team Announcements

Call for Testing

6. Other Meetings

#core-test, #test-chat-summary

Nikunj Hatkar 11:57 am on April 16, 2026
Tags: ,   

Team Chat Agenda: 16th April, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 16 April 2026, 03:00 PM UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#test-chat-agenda

Moses Cursor Ssebunya 5:37 am on April 14, 2026  

Test Team Voice Chat Summary: 2nd April, 2026

Receive the Huddle notes: 4/3/26 in #core-test written and improved from SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ AI notes for this huddle from 15:00:31 – 15:51:00 UTC . The WordPress Test Team held a monthly meeting discussing various ongoing projects, GitHubGitHub 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/ workflows, handbook updates, and upcoming contributor opportunities at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia. View huddle in channel

Attendees

@Moses Cursor, @nikunj8866, @Dilip Modhavadiya, @ozgursar, @r1k0, @noruzzaman, @Azhar Deraiya, @JuanMa, @Huzaifa Al Mesbah, @SAndrew, @Shazzad, and @Mohammed Kateregga

🌟 Summary

  • Props Bot GitHub Action Workflow
    • @Huzaifa Al Mesbah explained the proposed Props Bot would help identify contributors involved in pull requests and issues by automatically adding co-authors.[11:55]
    • The team discussed implementing a similar workflow to what GutenbergGutenberg 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/ and other WordPress projects use.[15:19]
    • The proposal aims to improve contributor recognition and tracking.[14:09]
  • Test Handbook Review
    • @Moses Cursor suggested a full review of handbook pages involving 3-4 team members.[27:01]
    • @JuanMa proposed assigning the task to contributors attending WordCamp Asia and reviewing progress afterward.[29:49]
    • Some handbook pages have already been updated, but a comprehensive review is needed.[31:09]
  • WordPress Playground Testing
    • @ozgursar volunteered to review and improve the existing WordPress Playground testing documentation.[33:00]
    • The team wants to update the documentation with new techniques and parameters.[33:53]
  • Testing Issues Tracking
    • @JuanMa suggested creating a bot to share the number of pending testing issues in the Slack channel weekly.[38:02]
    • The team agreed this would improve visibility of testing needs.[40:08]

☑️ Action items

🗣️ Announcements

This Slack Bot uses AI to generate notes, so some information may be inaccurate. They’re based on the huddle transcript and thread and can be edited anytime.

Props to the Slack Bot that helped make the summary and @nikunj8866 for Peer reviewing this

Moses Cursor Ssebunya 1:50 pm on April 2, 2026
Tags: , , test-voice-chat,   

Test Team Voice Chat Agenda: 2nd April, 2026

Here is the agenda for the upcoming Test Team Voice Chat scheduled for Thursday, 2nd April 2026 at 15:00 UTC which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

Props to @nikunj8866 for helping review this article and offering feedback

#core-test, #make-wordpress-orgupdates, #test-voice-chat, #web

r1k0 12:25 pm on April 1, 2026
Tags:   

Test Chat Summary: 26th March, 2026

On Thursday, 26 March at 17:00 GMT+3, <test-chat> started in #core-test facilitated by @r1k0. The agenda can be found here.

1. Attendance

In attendance was: @ozgursar @nikunj8866 @huzaifaalmesbah @mbigul @mohkatz @sonaliprajapati @juanmaguitar @mosescursor @mehrazmorshed (async) @sumitsingh (async)

2. Volunteer

This week’s facilitator was @r1k0

This week’s note-taker was @r1k0

3. Test Team Discussions

Review the current handbook PRs before publishing

The team discussed the progress of the handbook PR for the new documentation page and shared review updates. Initial feedback from @nikunj8866 noted that he had reviewed it and left some comments. He also pointed out that it would benefit from an additional review before publishing.

@r1k0 said he will leave a review, as it seemed good to him.

@ozgursar mentioned that it has corrected parts of the PR based on the feedback provided earlier.

@huzaifaalmesbah added they will review the PR today after work.

@nikunj8866 raised an issue that the new page still needed to be added to the handbook-manifest.json file so that it would appear in the handbook navigation.

@ozgursar asked @nikunj8866 where the new page should be placed, as it relates to another PR opened by @huzaifaalmesbah.

The team agreed that the most appropriate location would be under “Get set up testing”, with the page to be added there for now as the last item.
@r1k0 requested that the conversation be continued on GitHubGitHub 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/ to discuss the page creation and placement further.

The team also checked in on the progress of another handbook PR for a new documentation page.
@r1k0 mentioned he will take a closer look at it today and share his thoughts.

@mosescursor reviewed the PR and provided feedback.

@ozgursar Reviewed and helped co-author the PR.

@huzaifaalmesbah agreed to address the requested changes. After that, the page will be ready for publishing.

Proposed new handbook pages

The team discussed a proposal for adding new handbook content related to database inspection during testing.

@ozgursar pointed out it usefullness for testers, and asked where it fits best.

@nikunj8866 agreed that this page is necessary.

@r1k0 suggested it would fit better as part of the “Get Set Up for Testing” section, and @nikunj8866 also suggested including it as a subsection in the “Get Set Up for Testing”, not as a separate page.

In addition to the proposed method, @r1k0 suggested referencing alternative database access options, such as command-line access or plugins.

There was also interest in confirming how well the proposed setup would work with wp-env, @juanmaguitar confirmed that Docker additions should play nicely with wp-env.

@huzaifaalmesbah suggested grouping similar Docker-related setup options under a broader override-related section, which could help organize related documentation more clearly.

@r1k0 requested that team members add more comments to the GitHub issue to help refine the new page.

The team also discussed another proposed addition of a new page (Add Trac Keyword Triage Guide for Test Team Members) to the Test Handbook. There was general agreement to continue the discussion around implementation details in a pull request, which will help move the proposal forward and allow for more focused feedback.

@ozgursar suggested that the page could include a link to a related Chrome extension as an additional resource for contributors.

@juanmaguitar pointed out a related MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket that is highlighted for discussion: #8202, which explores incorporating some of the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.’s functionality directly into Trac.

@r1k0 encouraged contributors to share feedback in the Trac ticket.

Finally, @r1k0 raised the issues below for further contribution and discussion, and encouraged new contributors to share feedback or open pull requests to push the issues forward.

4. Open Floor

@juanmaguitar shared plans to publish a Make WordPress post about the WordPress Contributor Toolkit (Electron), highlighting its goal of reducing friction for code contributors, particularly first-timers. The tool, developed by the creator of WP Playground, is also intended to support Test tables at Contributor Days. Feedback and assistance to promote the tool at Contributor Days were welcomed.

@juanmaguitar welcomed everyone to a “Bug Scrub Session” scheduled in #core but was later postponed due to a timing conflict with the WordPress 7.0 RC2 release party.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

Props to @huzaifaalmesbah, @ozgursar and @nikunj8866 for helping review this article and offering feedback.

#test-chat-summary

r1k0 1:42 pm on March 25, 2026
Tags: ,   

Test Team Chat Agenda: 26th March, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 26 March at 17:00 GMT+3, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test, #test-chat-agenda

Nikunj Hatkar 2:23 pm on March 23, 2026
Tags: ,   

Core Test Team at WCAsia 2026: Contributor Day

Hello WordPress enthusiasts 👋

We’re thrilled to be gearing up for another exciting Contributor Day at WordCamp Asia (WCAsia) 2026, taking place on April 9, 2026 at the iconic Jio World Convention Centre in Mumbai, India! This year’s Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ is packed with exciting programming – including WordPress Release Panel Discussions, workshops, and the Open-Source Library.

Here’s a sneak peek at what we have planned for the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Team and how you can get involved.

🕰️ Important Times to Note: (All times are in IST, UTC+05:30)

  • 8:00 AM – Registration Open and Networking Time
  • 9:00 AM – Opening Remarks
  • 9:30 AM – Family Photo
  • 9:45 AM – Contributing to WordPress / Workshop / Open-Source Library
  • 10:00 AM – The Making of a WordPress Release: Conversations with Past Release Squad Members
  • 12:00 PM – Long Break / Networking
  • 1:45 PM – Group Photo( Table Leads, Facilitators & Open-Source Books)
  • 2:00 PM – Contributing to WordPress / Workshop / Open-Source Library
  • 4:30 PM – Closing Remarks
  • 5:00 PM – Contributor Day Wrap Up

For more details, please check the official schedule page.

Remote contributors are welcome to join via the #contributor-day channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.

👩🏻‍💻 Meet the Test Team Table Leads

We’re excited to introduce our Test Team Table Leads for WCAsia 2026:

In-Person Table Leads:

Their expertise and enthusiasm will be invaluable in ensuring a productive and engaging Contributor Day for all participants.

🎯 Core Test Team Goals

Our focus for the day revolves around meaningful and impactful contributions:

  • Onboard New Contributors: Provide guidance and mentorship to newcomers eager to join the Core Test Team.
  • Engage with WordPress Release Panel Discussions: Join the morning session to understand how the WordPress release cycle works, engage directly with contributors involved in the release, and experience the spirit of open-source teamwork firsthand.
  • Help with tickets that need testing (Core):
  • Help with tickets that need testing (GutenbergGutenberg 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/):
  • Test bugs or features and report new issues.
  • Improve Documentation: Enhance the clarity and comprehensiveness of testing guidelines.

Contributors with different skills, talents, and backgrounds can get involved in a variety of ways. Table leads and experienced contributors will be there to help you get started. You are welcome!

🌐 Collaboration and Community

Contributor Day at WCAsia 2026 isn’t just about work – it’s also about building connections and fostering community spirit. The WordPress Release Panel Discussions and Open Floor session will be a wonderful opportunity to connect with contributors shaping the next chapter of WordPress, ask questions, and celebrate the collective effort behind the project.

If you are new to core test contributions and want to stay updated, please join the #core-test channel on Slack.

We hold Patch Testing Scrub and Test Team Chat every Tuesday and Thursday at 15:00 UTC. Join us in the #core-test Slack channel to participate.

🔗 Helpful Resources

To make the most of Contributor Day, please review these resources before the event:

👀 Looking Ahead

As we gear up for this exciting Contributor Day in Mumbai, we look forward to the energy, conversations, and contributions that will shape the next chapter of WordPress. Whether you’re joining us in person or remotely, your contributions – big or small – make a real difference. 💪

Interested in Contributor Day but unsure if Test is the right fit for you? Check out Make WordPress’s Find Your Team tool to discover other opportunities.

Props to @ankit-k-gupta and @pavanpatil1 for peer review of this post. 🙌

#wcasia2026, #core-test

Moses Cursor Ssebunya 5:07 am on March 4, 2026  

Month in Test: March 3, 2026

Hello and welcome to another edition of Month in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Table of Contents

Calls for Testing 📣

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Test Handbook 📘

Merging of Test Handbook in GithubGitHub 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/

For the last few weeks, a good number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.

  • We want to inform that the Test Handbook is officially synced. There might be a couple of bugs and things that are not looking good pending to be fixed.
  • Feel free to give it a check here, and if you find any bugs, go to the GitHub repository and report them.
    • You can send a PR with the fix, or simply send the issue, and we will check it

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

Here’s a roundup of active tickets that are ready for testing contributions. Did you know that contributions to the Test Team are also a fantastic way to level up your WordPress knowledge and skills? Dive in to contribute, and gain coveted props 😎 for a coming release.

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Testing

a. Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment. Why?
It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets (4) have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

b. Bug Reproduction

It is necessary to confirm if the bug is happening under multiple conditions and environments, using the bug reproduction report in order to validate the issue.

The following tickets (141) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, then provide a bug reproduction report:

c. Test Team Issues

Here are the current activities being discussed in the Test Team Github:

  1. We need to review the Test Team Issues. If you have a possible solution, comment in the Issue or submit a PR.

2. GutenbergGutenberg 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/ Testing

👋 Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets (3) have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

b. Gutenberg Patch Testing

All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets (1) have been reviewed, and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉

  • none this Month

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
    • Weekly Patch Testing Scrub: Tuesday at 15:00 UTC (runs every week)
    • Weekly Test Chat: Thursday at 15:00 UTC (runs every week)
    • Monthly Voice Test Chat: First Thursday of each month at 15:00 UTC
  3. Call for Testing

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings. The schedule is being worked on and final schedule will be shared after finalizing the discussion

Current 2026 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

Props to @nikunj8866 for helping review this article and offering feedback

Ankit K Gupta 2:48 pm on February 17, 2026
Tags: , ,   

Test Scrub Schedule for WordPress 7.0

As you’re aware, WordPress 7.0 is slated to be the first major release of 2026, with the official release date set for April 9, 2026. As we gear up for this important milestone, our Test team will be shifting gears a bit. 

Starting from our upcoming weekly Patch Testing Session, we’ll be running a Test Scrub for WP 7.0 instead of the usual Future Milestone Tickets. These scrubs will focus specifically on tickets and issues related to the WordPress 7.0 milestone. It’s a great opportunity to contribute to this major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. and make a tangible impact on the final product. 

Where Will It Happen?

Each Test Scrub will take place in the #core-test channel on the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ at the same time as our regular weekly Test team meetings. If additional release‑focused scrubs are scheduled, they’ll also be announced in #core-test and added to the meetings calendar. 

What Tickets Will We Focus On?

We’ll primarily concentrate on tickets that are tagged Has Patch or/ Needs Testing for the 7.0 milestone. You can find these tickets in the 7.0 report on Trac. As the release moves through BetaBeta 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. and RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge., we’ll also highlight key features and regressions that need focused testing.

Interested in Leading a Test Scrub?

Did you know that anyone can lead a Test Scrub at any time? Yes, that means you can!

If you’re interested in leading a scrub, please reach out in the #core-test Slack channel with: 

  • The day and time you’re considering
  • The report or tickets you’d like to focus on (for example, a specific TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. report, a feature area, or a Beta/RC build)

If you’re planning a scrub that’s specifically focused on WordPress 7.0, that’s fantastic! We can add it to our schedule so the rest of the team knows to join in. Leading a scrub is a great way to contribute. 

Let’s Contribute Together

This is a perfect chance to get involved with the major release of WordPress 7.0, learn more about the release process, and help ensure the quality and stability of WordPress. Your contributions will make a difference, so join us for the Test Scrub sessions and be a part of this exciting release. 

Thank You ❤️

Thanks to everyone contributing time, testing, feedback, and expertise. Community testing plays a critical role in making each WordPress release successful.

Let’s work together to make WordPress 7.0 a smooth and high-quality release.

Props to @huzaifaalmesbah, @marybaum, and @nikunj8866 for pre-publish review.

#call-for-testing, #core

Huzaifa Al Mesbah 5:11 pm on February 14, 2026
Tags: ,   

Test Chat Summary: 12th February, 2026

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 GutenbergGutenberg 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 GitHubGitHub 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 TRACTrac 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 BetaBeta 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 CoreCore 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 UIUI 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