Category Archives: Summary

Image 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

Image 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

Image Nikunj Hatkar 5:31 am on April 14, 2026
Tags: , , ,   

WCAsia 2026: Contributor Day Recap

It was an incredible day of contribution, collaboration, and community spirit 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 2026 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/ in Mumbai! The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Team came together with energy and enthusiasm – both in person and online – to make WordPress better through testing.

Whether you tested a patch, triaged a ticket, explored WordPress 7.0 features, or just took your very first step into open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. contribution, every bit of effort mattered. 🙌

We had a wonderful mix of contributors – passionate newcomers and experienced testers – showing up from around the globe:

  • 57.1% participated in person
  • 42.9% contributed remotely
  • And most excitingly: 78.6% were first-time Core Test contributors!
Image
Image

🎯 What Did Contributors Work On?

  • Several contributors tested Core patches manually on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets including #64853, #64962, #65031, #65053, and #64944
  • Multiple contributors submitted Test Handbook pull requests to improve documentation (#120, #121, #128, #133, #147, #148)
  • Many first-time contributors explored WordPress 7.0 testing via the Help Test WordPress 7.0 guide
  • A few contributors also explored AI features in WordPress and 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/ 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.

💬 Community Voices

Here’s what some of our contributors shared:

  • “Remote participation from Latvia. Completed 4 patch tests and 1 triage contribution. Great experience working through real tickets with the team.” – @gaisma22
  • “I would love to continue contributing to the Test Team.” – @mehrazmorshed
  • “Explored WordPress 7.0 and tested AI features in WP. Also learned some basic features from the Team Lead and tested the Gutenberg plugin.” – @jetaldobariya1
  • “Thanks to all the table leads.” – @Dharm1025

The average contributor experience rating was an impressive 4.6 out of 5 ⭐ – a true testament to the welcoming and collaborative atmosphere the team created.

🙌 Our Contributors

A huge thank you to everyone who showed up and made this day special: @nazmul111, @mokshasharmila13, @vriti, @huzaifaalmesbah, @iamadisingh, @gaisma22, @abhishekfdd, @umeshsingla, @mehrazmorshed, @ismail0071, @abduremon, @jetaldobariya1, @pratikmandaliya, @Dharm1025

🏅 Contributor Badges

Badges are being assigned to all eligible contributors. Thank you for your patience! Keep an eye on upcoming weekly Test Team updates on make.wordpress.org/test for badge confirmations.

🗓️ Core-test Meetings

The Test Team meets every week in the #core-test 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/. Check out the current meeting schedule and drop by to say hi, ask questions, or just lurk and learn!

Contributor Day may be over, but your journey with the Test Team doesn’t have to stop here. From exploring patches to writing your first test, we’re here to support you every step of the way. Check out the Test Handbook and stay tuned for more ways to contribute.

Thank you for being part of the WordPress community – you made Contributor Day at WCAsia 2026 truly special. ✨

Have you joined the test team yet?

Join the Test Team

Props @ankit-k-gupta and @pavanpatil1 for pre-publish review.

#wcasia2026, #contributor-day, #core-test, #recap

Image 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

Image 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

Image Manuel Camargo 1:39 pm on February 6, 2026
Tags:   

Test Chat Summary: 5th February 2026

1. Attendance

In attendance was:
@fakhriaz @huzaifaalmesbah @ozgursar @supernovia @mosescursor @sajib1223 @andrewssanya @mohkatz @zuveria @r1k0 @sirlouen

2. Volunteer

3. Test Team Discussions

Switching to Monthly Newsletter

The team discussed changes to the monthly newsletter format. The decision was made to remove the “tests to be done” section and replace it with a new “call for testing” section that aggregates requests from other groups. Additionally, the newsletter will include announcements, news, and ideas from team members. @mosescursor will comment on the related 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 with further details.

New Triage Guide

@sirlouen presented the diagram proposed by @juanmaguitar in the “Add TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Keyword Triage Guide for Test Team Members” initiative. During the discussion:

  • @ozgursar raised concerns about whether bug reproduction should be included, noting it could be confusing.
  • @r1k0 commented that the guidance on what to write for expected results is not clear enough.

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

Announcements for Test Team Promotions

Promotions were announced for the following team members: @ozgursar, @r1k0, @juanmaguitar, and @huzaifaalmesbah.

4. Open Floor

  • @sirlouen expressed hope that the team can move toward an automated testing protocol in the future. Several ideas were discussed around improving the onboarding experience for new contributors:
  • @shazzad suggested adding a special keyword to identify easy tickets for new test team members.
    • @fakhriaz agreed with the idea.
    • @supernovia suggested the name good-first-test for this keyword.
    • @sirlouen had some concerns looking at the triage workflow: when a new test ticket appears in chat, a team member should triage and review it, removing the needs-testing keyword if the ticket cannot be tested, but leaving it if it can be tested. Placing the good-first-test keyword on tickets doesn’t seem to find a good place in this workflow. Further refinement is required to confirm that this keyword will truly fit.
    • @shazzad will open a ticket in the GitHub test-handbook repository to formalize this idea.
  • The team also discussed the need for weekly test team updates on current Needs Reproduction and Needs Patch Testing tickets. @mosescursor will handle this responsibility until @nikunj returns.
  • @mosescursor asked if @r1k0 would be joining the contribution day in Uganda on March 14. @r1k0 will check his schedule and confirm.
  • @sirlouen reminded the team that any AI tools used during testing should be noted in the footnotes of test reports.
  • @mosescursor will request huddle permission from the 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. team to facilitate future voice chats.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

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

#test-chat-summary

Image Ozgur Sar 1:01 pm on January 31, 2026
Tags: ,   

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 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/ issues requiring team review:

A proposed new version of 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. 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 filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. 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 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..

4. Open Floor

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 2026 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/

@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

Image JuanMa Garrido 3:33 pm on January 29, 2026
Tags: ,   

Test Chat Summary: 22nd January 2026

On Wednesday, 22 January 2026, 03:01 PM UTC, <test-chat> started in #core-test facilitated by @juanmaguitar. The agenda can be found here.

1. Attendance

In attendance was:
@juanmaguitar @nikunj8866 @sirlouen @mosescursor @ozgursar @pavanpatil1 @sajib1223 @r1k0 @mohkatz @fakhriaz @alexcu21 @huzaifaalmesbah

2. Volunteer

This week’s facilitator was @juanmaguitar

This week’s Note-taker was @juanmaguitar

3. Test Team Discussions

“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. testers” for the new Test Contributor Pathway course

@sirlouen announced that the Test Contributor Pathway course will be launching on the Learn site in the coming weeks. The team is looking for beta testers to review the videos and provide feedback. Community members interested should contact @sirlouen directly for private access.

Creating a new page in the handbook with a “template” for Test Chats

The team discussed creating documentation for facilitating test chat meetings. @sirlouen explained the goal is to document templates and guidance so anyone can run a test chat. @juanmaguitar noted he’s currently following steps from a previous meeting.

Contributors can submit pull requests to the test-handbook GitHub repository, or open issues with ideas if a full PR feels too daunting.

Add labels to posts that are regularly posted on make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//test

@juanmaguitar proposed adding consistent tags (week-in-test, test-chat-summary, test-chat-agenda) to recurring posts to improve discoverability, similar to Gutenberg posts. See full suggestion in Slack.

The discussion focused on tags vs categories. The main advantage of tags is they persist when duplicating posts or using templates, while categories can be forgotten. However, categories are prominently displayed in the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. @mosescursor noted the “Kibble” default categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. is misconfigured.

@juanmaguitar will open 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 (#109) to continue the discussion. The topic requires more thinking and will be revisited once there’s more consensus.

Call for help, building the 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/ bot for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

@sirlouen requested help building a Slack bot for Core testing announcements, similar to the existing Gutenberg announcer. The goal is to automatically notify #core-test whenever a needs-testing tag is added to a Core ticket.

PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php scripts that interact with TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. already exist at meta.trac.wordpress.org. More details are available in Trac ticket #8157. @juanmaguitar expressed interest in helping with this.

4. Open Floor

No items were raised during the open floor.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

Props to @sirlouen for reviewing this post

#core-test

#test-chat-summary

Image Nikunj Hatkar 11:37 am on January 19, 2026
Tags:   

Test Chat Summary: January 14th, 2026

On Wednesday, 14 January 2026, 02:00 PM UTC, <test-chat> started in  #core-test facilitated by @nikunj8866. The agenda can be found here.

1. Attendance

In attendance was:
@nikunj8866 @fakhriaz @huzaifaalmesbah @sirlouen @shanemuir @harshalkadu @pavanpatil1 @r1k0 @369work @saqib @juanmaguitar @ozgursar @hage (async) @mebo (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

  1. Time to Comment Back/Update the Get Set Up for Testing Page.
  2. Time to Review/Update the Test Core Tickets with Playground Page.
  3. @sirlouen shared 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 #99 proposing a redesign of the Test Team Updates report.
    • The new format aims to be simpler, focusing on 4 reports across 2 sections (CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and Editor).
    • Only two key data points will be included: Current totals per categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. and 2-week changes per category (Closed tickets were considered low value and can be removed.)
    • @nikunj8866 noted the discussion, will review the GitHub thread in detail, and prepare a draft for the next report for team review before publishing.
  4. @sirlouen mentioned that the new Test Reports should be officialized after the training program ends, around February.
    • GitHub issue #100 – Officialize the Test Reports was shared as a follow-up.
    • No further action required at this time; the topic will be revisited after the training period.
  5. @juanmaguitar introduced an experimental Playground-based tool to simplify the WordPress testing setup(https://github.com/Automattic/experimental-wp-dev-env).

4. Open Floor

  • @sirlouen proposed moving the Test Team meetings from bi-weekly to weekly during the training program to increase participation and help trainees get involved in running meetings.
  • It was suggested to change the meeting day and time to better align with training sessions, moving away from Wednesdays.
  • A new proposed meeting structure was shared:
    Weekly Patch Testing Scrub: Tuesday @ 3:00 PM GMT
    Weekly Test Team Chat: Thursday @ 3:00 PM GMT
    Monthly Recorded Voice Session: First Thursday of each month @ 3:00 PM GMT
  • The monthly voice session will be recorded (via Huddle or Zoom) to allow asynchronous participation.
  • Patch testing sessions will also run weekly, with @nikunj8866 facilitating the next session, followed by training program members for the coming weeks.
  • The proposal has been documented in GitHub issue #103 for feedback and discussion before finalizing.
  • Once finalized, the Meetings calendar will be updated accordingly.
  • @huzaifaalmesbah asked about supporting TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. diff/patch files in WordPress Playground to make testing easier for contributors.
    • @sirlouen shared that this idea had been discussed earlier with the Playground team, but it does not seem easy to implement.
    • A GitHub PR-based workflow was suggested as a more modern and preferred approach.
    • @sirlouen followed up by raising the question in the #playground 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/ channel to explore possible alternatives, such as using a diff URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org.
  • @ozgursar asked whether there is any priority (such as milestones) when querying tickets in Trac.
    • @sirlouen explained that once the reports are officially active, milestoned tickets would naturally take priority.
    • Since the reports are not official yet, contributors are free to pick tickets in any order for now.

5. Announcements

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
  3. Call for Testing

6. Other Meetings

#core-test

Image Moses Cursor Ssebunya 1:55 pm on December 22, 2025
Tags: , , , , ,   

Test Chat Summary: December 17th, 2025

On Wednesday, December 17th, 2025 at 04:00 PM GMT+2, started in#core-test facilitated by @mosescursor. The agenda can be found here.

1. Attendance

In attendance was:
@fakhriaz @nikunj8866 @huzaifaalmesbah  @noruzzaman  @sirlouen @oglekler @r1k0 @abduremon @Dhruvang21 @gautammkgarg @mebo

2. Volunteer

Meeting started by explaining Note takers and Facilitators so people can take up the roles.

  1. Note takers are simply people who summarize the happening of the Test Chat and they always publish a test Chat summary like this one here.
  2. Facilitators are simply people that chair or facilitate a test team chat.
    These follow the agenda that is proposed and ensure that every one gets a voice.
    A sample Meeting is like the one held here.

These 2 can be done by the same person in the same instant however we encourage multiple people to do it to increase on the proof reading and collaboration

3. Test Team Discussions

  1. Time to Review/Update the Get Set Up for Testing Page.
  2. Time to Comment Back/Update the Test Team Reps Page.
  3. Update on Test Handbook: New pages for Feature & Enhancement Testing (#90), E2E Testing (#91), and Patch Testing Scrubs (#92) are available; contributors can update content via 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/ issues.
    • @sirlouen got to a conclusion that currently we don’t have enough resources to have the wheel moving
      • all the areas mentioned above require a good thought and a suggestion to expand the team was brought up.
  4. Test Team Training Program & Restructuring Plans for 2026
    • @sirlouen is leading the program.
    • Previously, mentorship was insufficient so now a full training was advised. A program in the test team that will bring in Champions
      • A call for as many people as possible was made. People that will be committed to the program and see it through
    • @nikunj8866 sighted it as a great learning opportunity for anyone who wants to become a future Test Team representative.
      • @sirlouen added that it won’t only make team reps but also Power Members.
    • @sirlouen will pause current Handbook activity in preparation for the program in the next 2 weeks. Announcement made here highlighting the requirements to join and all the information about the program.

4. Open Floor

Image
  • We have introduced a bot that informs of new 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/ issues coming for testing. This posts directly in the 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/ channel
    • @sirlouen recommended adding an emoji like this :white_check_mark:  if you are going to be doing the testing report.
    • This helps for quick assignment of tasks and getting them cleared quickly.
    • Here people get a chance to know the tests required and even do them without having to wait for a Patch-testing session.
      • Infact this could also end the patch testing sessions when the new training is implemented
        • With this new notifier, anyone could jump in

5. WordPress Ecosystem Announcements

6. Other Meetings

We usually have 2 meetings held every week. This is the last test-chat meeting for this year and Tomorrow’s patch testing session will be the last for this year.

  • Happy Festivities, See you again Next Year.
  • Happy new Year 2026

#core-test, #fse-outreach-program, #full-site-editing, #gutenberg, #make-wordpress-orgupdates, #web