Tag Archives: core-test

Huzaifa Al Mesbah 6:17 am on October 15, 2026
Tags: core-test,   

Team Chat Agenda: 15th October, 2026

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

Erick Wambua 11:52 am on October 5, 2026
Tags: core-test, , ,   

Month in Test: October 05, 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. https://github.com/

For the last few months, 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 (19) 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 (128) 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 (14) 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 🎉

@softglaze, @369work, @habiburdev, @ekamran, @dhavalkapadane, @jdab, @rahultank, @chinmoy709, @arifulislam1, @ahsannayem

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
    • Weekly Patch Testing Scrub: Second and Fourth Thursday of the Month at 15:00 UTC
    • Weekly Test Chat: Third Thursday of the Month at 15:00 UTC
    • 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 @huzaifaalmesbah for peer reviewing this post

#core-test, #fse-outreach-program, #gutenberg, #make-wordpress-orgupdates

Huzaifa Al Mesbah 6:57 am on September 29, 2026
Tags: , core-test   

Planning to Join the Test Team Table at Contributor Day?

A little preparation before 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://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ can help us spend less time on setup and more time actually testing and contributing together!

Whether you are heading to an in-person Contributor Day this week—such as WordCamp Sylhet (Bangladesh) or WordCamp Rajasthan (Jaipur, India) or participating remotely from your desk, the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Team welcomes you.

As celebrated in the recent Thank You to the WordPress 7.1 Test Contributors announcement, India (31 contributors) and Bangladesh (10 contributors) led the world as the top two countries in test contributions, making up nearly half of all testers globally. Now, with the WordPress 7.2 cycle underway, we are excited to carry that incredible momentum straight into our upcoming contributor tables!

And there is even more good news! 🎉

WordPress recently introduced the Contributor Day Toolkit Maintained By JuanMa Garrido, designed specifically to make getting started at Contributor Day easier and faster.

Before Contributor Day: Friction-Free Setup

Setting up a local WordPress development environment traditionally involves installing and configuring tools like GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/, Node.js, npm, Docker, and SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/.. For someone making their first contribution, that setup alone can take a significant amount of time.

To save time and venue Wi-Fi bandwidth, we recommend checking out these options ahead of time:

Don’t worry if you cannot complete everything beforehand. That’s exactly what the table is there for! Experienced table leads and mentors will be there to help you get started, answer questions, and work through your first contribution together. 💪

What Can We Work on at the Test Table?

With the Roadmap to 7.2 now underway, our primary focus is testing upcoming features, reproducing bug reports, and verifying patches before they land in core.

The #core-test 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 publishes a Weekly Testing Digest every Monday highlighting current issues, PRs, and tickets that need testing. Here are direct opportunities waiting for testing:

  • WordPress 7.2 Core TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Tickets: Browse the Core Trac needs-testing queue to reproduce bug reports or verify patches.
  • Gutenberg (BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor) Issues & PRs: Help test open Gutenberg Issues and test proposed fixes in Gutenberg Pull Requests.

When filing your feedback on tickets, you can refer to the handbook’s Issue Reproduction and Patch Testing templates, along with the Trac Keyword Triage Guide, to write clear, actionable reports.

Joining Remotely?

Can’t attend an event in person? You can still participate! Jump into the #core-test and #contributor-day channels on Make WordPress Slack anytime. Team reps and contributors will be active online to answer questions and collaborate with you.

Want to Stay Involved After Contributor Day?

Contributor Day can be your starting point, not the end! 🙂

  • You can join the Test Team meetings every Thursday at 15:00 UTC in #core-test on Slack. The meetings rotate through the following schedule:
    • Team Voice Test Chat: 1st Thursday of each month at 15:00 UTC
    • Patch Testing Scrub: 2nd Thursday of each month at 15:00 UTC
    • Test Team Chat: 3rd Thursday of each month at 15:00 UTC
    • Patch Testing Scrub – Gutenberg: 4th Thursday of each month at 15:00 UTC
  • Follow the Make WordPress Test blog for bi-weekly updates, calls for testing, and weekly digests to stay familiar with current priorities.

And Most Importantly…

You don’t need to be an experienced tester or developer to join the Test table.

Testing is one of the most rewarding ways to learn how WordPress works behind the scenes. Come with your laptop, your curiosity, and your questions—we’ll work through the rest together.

Looking forward to testing and contributing with you! 🚀

Props to @krupajnanda for putting this post together, and @noruzzaman and @r1k0 for reviewing it.

Huzaifa Al Mesbah 5:03 pm on September 18, 2026
Tags: , core-test,   

Thank You to the WordPress 7.1 Test Contributors

WordPress 7.1 is here, and it wouldn’t have been possible without the incredible effort of the testing community. Behind every stable release is a dedicated group of people who download 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. versions, apply patches, reproduce bugs, and report what they find. They are the safety net that catches issues before they reach millions of WordPress users. This post is a celebration of those people.

7.1 Testing, By the Numbers

These numbers were compiled using the WordPress Test Contribution Tracker, an automated tool that scans TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets, classifies test contributions, and identifies new contributors. If we missed your contribution or a number looks off, let us know in the comments — we’ll gladly fix it.

Note on Data Scope: This report specifically tracks testing and bug reproduction contributions submitted on WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Trac tickets for the 7.1 milestone. Testing contributions made directly on the Gutenberg GitHub repository are not captured in this automated tracker.

During the WordPress 7.1 release cycle, the testing community achieved something remarkable:

– 337 Core Trac tickets were evaluated and tested
– 84 unique contributors participated in testing and bug reproduction
– 50 of them were new contributors — testing WordPress without a Test Contributor badge yet
– 75 contributors tested patches directly
– 21 contributors helped reproduce confirmed bugs
– 20+ countries across 5 continents were represented

That’s 60% of all test contributors being new candidates to WordPress testing. If that’s not a sign of a growing and healthy community, we don’t know what is.

A Global Effort

Testing WordPress is truly a worldwide effort. During the 7.1 cycle, contributors joined in from 20+ countries across 5 continents, working across time zones and languages to make WordPress better for everyone.

🇮🇳 India led the way with 31 contributors — more than a third of all testers. 🇧🇩 Bangladesh followed with 10 contributors, and 🇺🇸 United States contributed 7. Rounding out the top countries: 🇵🇰 Pakistan (4), 🇪🇸 Spain (3), 🇫🇷 France (2), and 🇵🇭 Philippines (2).

Contributors also joined from 🇧🇹 Bhutan, 🇧🇬 Bulgaria, 🇨🇿 Czech Republic, 🇮🇹 Italy, 🇯🇵 Japan, 🇰🇪 Kenya, 🇱🇮 Liechtenstein, 🇱🇹 Lithuania, 🇳🇱 Netherlands, 🇵🇱 Poland, 🇷🇺 Russia, 🇹🇳 Tunisia, and 🇺🇬 Uganda — each with 1 contributor proving that every single test makes a difference.

Every Contribution Counts

We want to recognize every single person who tested a ticket, left a “reproduced” comment, or tried a patch during the 7.1 cycle. Whether you tested 12 tickets or just 1, you made a difference.

Here’s the full list of all 84 contributors who participated in testing or reproduction for WordPress 7.1:

@abcd95 @adamsilverstein @afercia @alexodiy @alshakero @ankitkumarshah @anukasha @cweiske @darshitrajyaguru97 @deepakprajapati @dhrupo @dhruvang21 @drwpcom @eishanoor @ekamran @fakhriaz @fatimatd @fushar @gaurangsondagar @gazipress @gulamdastgir04 @habiburdev @hbhalodia @hmbashar @huzaifaalmesbah @iamchitti @iamraju @jadavsanjay @jamesbregenzer @jeffpaul @joedolson @jonsurrell @juliemoynat @khokansardar @liaison @luisdavid01 @madhavishah01 @manhar @manishxdp @masteradhoc @mdridipu @mirmpro @mkrndmane @mosescursor @mukesh27 @n8finch @nadabulija @nazmulasif @noruzzaman @ozgursar @pavanpatil1 @pedrofigueroa1989 @phpbits @r1k0 @RavanH @ravichudasama01 @rejaulalomkhan @reneyap @rishabhwp @robert681 @rollybueno @sanayasir @SergeyBiryukov @shailu25 @shamimmoeen @shreyasikhar26 @simison @SirLouen @softglaze @soyebsalar01 @sumitbagthariya16 @swapnil1010 @tusharaddweb @tusharbharti @tyxla @ugyensupport @valani9099 @vedantere @vgnavada @westonruter @wildworks @yashjawale @yogeshbhutkar @yusufmudagal

Thank you, all of you. WordPress 7.1 is better because of your time and effort.

Get Involved — Help Test WordPress 7.2

The WordPress 7.2 cycle is already underway, and we’d love for you to join the testing effort. Testing is one of the most impactful ways to contribute to WordPress — and you don’t need to be a developer. If you can install WordPress, follow instructions, and describe what you see, you can be a test contributor.

Here’s how to get started:

1. Choose Your Setup

Depending on what you want to test and your setup preference, you can choose:

  • WordPress Playground — The fastest way to test directly in your browser with zero setup (best for quick PR reviews).
  • WordPress Contributor Toolkit by JuanMa — A zero-prerequisite desktop app (user guide) that lets you apply and test both .patch/.diff files and 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/ PRs locally without needing Docker.
  • Local Docker Environment — Best for running automated test suites (PHPUnit, E2E) and advanced command-line development.
  • Test Gutenberg — Follow this guide to test blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor features and pre-release 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/ versions.

2. Find Something to Test

There are tickets and PRs waiting for testers right now:

You can also check the Calls for Testing on the Test Team blog — these are focused, guided testing tasks with step-by-step instructions, perfect for new contributors.

3. Test and Report

Once you’ve found a ticket, there are two main types of testing you can do:

  • – Issue Reproduction — Confirm that a reported bug is real by following the steps and describing your results. Use the Issue Reproduction template from the handbook.
  • – Patch Testing — Apply a patch and verify it fixes the issue (or delivers the expected feature). Watch for regressions where the patch fixes one thing but breaks another. Use the Patch Testing template from the handbook.

Both templates include fields for your environment (OS, 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/index.php version, WordPress version, browser) and space for your results. Just copy, fill in, and post as a comment on the ticket.

4. Help with Triage

If you’re comfortable navigating Trac, you can also help with ticket triage. When a ticket is tagged `needs-testing`, testers evaluate it and decide the next step. The Trac Keyword Triage Guide explains the four keywords testers manage (`needs-testing`, `needs-test-info`, `dev-feedback`, `needs-refresh`) and includes ready-to-use comment templates.

5. Get Recognized

Contributors who provide meaningful test contributions — reproduction reports, patch tests, unit tests, or documentation updates — earn the Test Contributor badge on their 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/ profile. Learn more at Test Team Profile Badges.

Join the Community

Let’s keep making WordPress better, one test at a time. 🎉

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

#7-1, #core-test, #make-wordpress-orgupdates

Nikunj Hatkar 1:47 pm on September 17, 2026
Tags: core-test,   

Team Chat Agenda: 17th September, 2026

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

Nikunj Hatkar 12:44 pm on August 24, 2026
Tags: core-test,   

Test Chat Summary: August 20th, 2026

On Thursday, 20 August 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:
@nikunj8866 @ozgursar @softglaze @ikamal @r1k0 @mosescursor @huzaifaalmesbah @rejaul

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

  1. Test Team Reps: Call for Nominations
    • Nominations for the next Test Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. term are open until 2026-09-12 00:00.
    • To nominate someone (or yourself), comment on the post.
    • Private nominations can be sent to @mosescursor or @nikunj8866 in 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/.
  2. Revise Test Team Rep duties and qualifications
    • @nikunj8866 has already reviewed the PR and finds it good to merge.
    • Some feedback already exists on the PR; @mosescursor to take a look.
    • Anyone who hasn’t reviewed yet is encouraged to leave feedback directly on the PR.
  3. [Issue Reproduction] Missing guidance on testing unexecutable code paths by forcing conditions
    • Team agreed a common section should be added to the handbook for this scenario.
    • @nikunj8866 proposed a simple addition, as suggested by @huzaifaalmesbah: when a condition can’t be reproduced locally, tag the reporter and add a comment with the needs-test-info keyword.
  4. Proposal: extend TestFlow to help moderators prepare a session, not just run one
    • @ozgursar noted @softglaze found some bugs and will test them as time allows.
    • @ikamal has already commented on the issue.
    • All members encouraged to read the issue and share their thoughts directly in the 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/ thread.
  5. Recognize WordPress 7.1 Test Contributors – Badge Awards & Blog Post
    • Following the same approach used for 7.0, the team will recognize WordPress 7.1 test contributors via badges and a blog post.
    • @huzaifaalmesbah to prepare the contributor docs, following the same process as last time.
    • Once the docs are ready, @mosescursor will review and assign badges to eligible contributors.

4. Open Floor

There were no additional topics raised during the open floor session.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

#core-test, #test-chat-summary

Nikunj Hatkar 2:27 pm on August 20, 2026
Tags: core-test,   

Team Chat Agenda: 20th August, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 20 August 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 2:47 pm on August 12, 2026
Tags: core-test,   

Test Chat Summary: August 6th, 2026

Huddle notes: 8/7/26 in #core-test. AI took notes for this huddle from 1:02:18 AM – 1:59:19 AM GMT+10. WordPress test team reviewed four 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, closed learner pathways, assigned handbook documentation for test flowFlow Flow is the path of screens and interactions taken to accomplish a task. It’s an experience vector. Flow is also a feeling. It’s being unselfconscious and in the zone. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it. 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., and identified blockers requiring external team coordination.

Attendees

@MosesCursor, @ikamal, @huzaifaalmesbah, @ozgursar, @r1k0, @ismail0071, and @mbigul

Summary

Test Handbook Restructuring for Multiple Domains

  • @huzaifaalmesbah proposed keeping issue #111 open and splitting into sub-issues or assigning to new contributors for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. testing guidance. [30:58]
  • @ozgursar noted restructuring requires moving all current content under core directory, affecting entire handbook structure. [32:28]
  • @huzaifaalmesbah and @ozgursar agreed to start with core and 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/ directories, deferring AI and performance sections until content exists. [33:31]
  • @Moses Cursor proposed reaching out to AI and performance teams for testing content; team agreed external input is necessary before proceeding. [36:02]

Learner Pathways Issue Closure

  • @huzaifaalmesbah confirmed learner pathways look good for beginners and are ready to close. [26:16]
  • @Moses Cursor closed issue after team confirmation. [26:51]

Test Flow Plugin Documentation

  • @ozgursar reported plugin is working and ready for use via playground; only handbook documentation remains. [39:33]
  • @r1k0 suggested adding plugin documentation as a section in moderator guide rather than standalone page. [48:41]
  • @huzaifaalmesbah proposed including test report plugin and chat monitor guide in patch testing section. [53:00]
  • @ozgursar will submit plugin to WordPress directory from personal account after handbook documentation is complete. [45:08]

Team Goals and Initiatives Issue

  • @Moses Cursor noted issue #9 is unclear and suggested retiring or deferring for internal discussion with Nikunj. [17:07]
  • @huzaifaalmesbah recommended keeping issue open and following other teams’ goal structures before proceeding. [18:49]

Tags vs. Categories Discussion

  • @ozgursar raised whether handbook switched from categories to tags; @r1k0 confirmed not yet and questioned necessity. [17:44]
  • @r1k0 identified issue #109 as related tags discussion and committed to reviewing and posting feedback. [21:17]

Announcements and Schedule

  • Weekly patch testing scrub: 2nd and 4th Thursday at 15:00 UTC; weekly test chat: 3rd Thursday; monthly voice chat: 1st Thursday.
  • Multiple calls for testing available including WordPress 7.1, media editor, and responsive styling.

Action items

  • @ikamal create handbook section documenting test flow plugin in moderator guide. [47:06]
  • @ozgursar submit test flow plugin to WordPress directory after handbook documentation complete. [45:08]
  • @Moses Cursor coordinate with AI and performance teams to identify testing content and requirements. [36:02]
  • @r1k0 review issue #109 on tags and post feedback. [21:17]

Files and media

#test-chat-summary

Moses Cursor Ssebunya 2:51 pm on August 6, 2026
Tags: core-test,   

Team Chat Agenda: 6th August, 2026

Here is the agenda for the upcoming Test Team Voice Chat scheduled for Thursday, 6 August 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 3:00 am on August 4, 2026
Tags: core-test, , ,   

Month in Test: August 03, 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. https://github.com/

For the last few months, 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 (15) 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 (133) 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 (14) 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 🎉

@khushdoms, @jsmansart, @ankitkumarshah, @soyebsalar01, @poojapadamad, @gaurangsondagar, @manhar, @westonruter, @khushi1501

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
    • Weekly Patch Testing Scrub: Second and Fourth Thursday of the Month at 15:00 UTC
    • Weekly Test Chat: Third Thursday of the Month at 15:00 UTC
    • 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 @sajib1223 @huzaifaalmesbah @nikunj8866 for peer reviewing this post

#core-test, #fse-outreach-program, #gutenberg, #make-wordpress-orgupdates