Category Archives: Summary

Erick Wambua 12:13 am on September 5, 2026
Tags:   

Test Chat Summary: September 3rd, 2026

Huddle Notes: 9/4/26 in #core-test.
AI took notes for this huddle from 1:01:42 AM – 2:25:23 AM GMT+10. The test team reviewed three 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/PRs for the Test handbook, discussed extending the 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. with difficulty ranking and 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/ integration, and explored separating 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. testing from unit testing keywords

Attendees

@mosescursor, @r1k0, @ozgursar, @jns141191, @huzaifaalmesbah, @pbearne, @mohkatz and @khushdoms

Summary

Test Flow Plugin Extension Proposal

@ozgursar noted that Soft Glaze aims to 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. tickets by difficulty before sessions, helping moderators select appropriate tasks. [7:51]

@jns141191 raised concern that duplicate tickets spanning years aren’t surfaced, making discovery difficult. [10:18]

@r1k0 identified that the “good first bug” keyword doesn’t necessarily indicate ease of testing, conflating patch difficulty with test difficulty. [11:33]

@r1k0 proposed exporting session history; @pbearne suggested auto-generating posts summarizing completed tickets instead. [17:30]

Slack integration flagged for deferral pending 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 discussion on privacy and security concerns. [19:00]

Pull Requests #186 and #183 Status

PR #186 awaits author updates to address @ozgursar‘s comments before merge. [22:43]

PR #183 has two approvals and @ozgursar‘s support but needs minor rewording before merging. [26:59]

Test Contributor Badge Recognition

@r1k0 fully supports proactively awarding badges to contributors meeting requirements without requests. [30:54]

@pbearne argued that “needs testing” conflates UI testing with unit testing and needs separate keywords for clarity. [33:18]

@r1k0 agreed to discuss keyword separation with the Meta team; @pbearne suggested also exploring E2E/puppet testing tags. [36:28]

Current “need testing” keyword visibility is low; @r1k0 proposed tagging all milestone tickets to increase discoverability. [31:38]

Unit Testing AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) and Coverage

@r1k0 initially meant to ask about Unit testing in the open floor section, but it came up earlier in the session.

@pbearne shared that WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is at 40.47% code coverage; the goal is 80% before retirement. [41:12]

@pbearne noted AI tools simplify test writing; a local Docker setup is required, and writing unit tests is not exclusively reserved for committers. [40:05]

@pbearne offered to mentor anyone interested in writing unit tests and shared a Codecov link for coverage analysis.

@pbearne recommended documentation in the repo README and suggested splitting handbook guidance by skill level (coder vs. UI tester). [45:05]

Announcements and Ecosystem Updates

  • WordPress 7.1 “Mary Lou” released; 7.2 seeking volunteers; 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/ 23.9 and multiple ecosystem updates posted.
  • New WordPress community groups on events.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/ are available for testing and feedback.

Action items

@r1k0 will pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” Soft Glaze to update PR #186 with @ozgursar‘s requested changes. [22:43]

@r1k0 will ping Moses to update PR #183 with suggested rewording. [27:55]

@ozgursar will summarize today’s discussion and ping Soft Glaze for feedback on the test flow proposal. [48:47]

@r1k0 will discuss separating “needs testing” keywords (UI vs. unit vs. E2E) with the Meta team. [36:28]

Files and media

#test-chat-summary

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

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

Moses Cursor Ssebunya 2:47 pm on August 12, 2026
Tags: ,   

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 3:00 am on August 4, 2026
Tags: , , ,   

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

Nikunj Hatkar 6:47 am on July 21, 2026
Tags: ,   

Test Chat Summary: July 16th, 2026

On Thursday, 16 July 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 @huzaifaalmesbah @r1k0 @andrewssanya @mosescursor (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

  1. Officialize the Test Reports
    • @huzaifaalmesbah suggested this should go through 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, or a Meta TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket should be opened.
    • @nikunj8866 will open a Meta Trac.
  2. Feature and enhancement testing Page
    • @huzaifaalmesbah noted the existing Patch Testing page likely already covers this, and leaned toward improving it rather than creating a new page.
    • @ozgursar referenced the recently updated Call for Testing page as relevant context.
    • Team agreed the existing documentation already covers the proposal.
    • Issue closed by @nikunj8866, with a comment referencing today’s discussion.
  3. Add page with current team goals/initiatives
    • @ozgursar raised whether implementing @sirlouen suggestion would require switching from categories to tags – noting this has come up in prior test chats too.
    • @r1k0 agreed with the tags approach and asked if a current “goals” post already exists – confirmed no.
    • Team agreed to follow @sirlouen suggestion: add a link to the initiatives tag in index.md.
    • Open to anyone – a PR is welcome for this change.

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

Huzaifa Al Mesbah 7:19 am on July 6, 2026
Tags: , ,   

Thank You to the WordPress 7.0 Test Contributors

WordPress 7.0 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.0 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. 

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

– 427 CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Trac tickets were tested
– 132 unique contributors participated in testing and bug reproduction
– 89 of them were new contributors — testing WordPress for the very first time and without a Test Contributor badge yet
– 113 contributors tested patches directly
– 34 contributors helped reproduce confirmed bugs
– 25+ countries across 6 continents were represented

That’s 67% of all test contributors being completely new 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.0 cycle, contributors joined in from 25+ countries across 6 continents, working across time zones and languages to make WordPress better for everyone.

🇮🇳 India led the way with 47 contributors — more than a third of all testers. 🇧🇩 Bangladesh followed with 15 contributors, and 🇺🇸 United States contributed 11. Rounding out the top countries: 🇩🇪 Germany (4), 🇫🇷 France (3), 🇪🇸 Spain (3), 🇵🇭 Philippines (3), 🇯🇵 Japan (2), 🇦🇺 Australia (2), and 🇺🇬 Uganda (2).

Contributors also joined from 🇰🇪 Kenya, 🇵🇰 Pakistan, 🇧🇹 Bhutan, 🇩🇿 Algeria, 🇳🇱 Netherlands, 🇦🇹 Austria, 🇹🇳 Tunisia, 🇪🇬 Egypt, 🇻🇳 Vietnam, 🇵🇹 Portugal, 🇳🇵 Nepal, 🇮🇹 Italy, 🇸🇪 Sweden, and 🇨🇭 Switzerland — each with 1 contributor proving that even a 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.0 cycle. Whether you tested 36 tickets or just 1, you made a difference.

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

@369work @abcd95 @abdullah17 @abduremon @adnanhyder @agnieszkaszuba @alh0319 @alexodiy @amesplant @amin7 @andrewssanya @ankitkumarshah @arkaprabhachowdhury @audrasjb @benniledl @berislav.grgicak @chexee @darshitrajyaguru97 @dhruvang21 @dhrumilk @dilip2615 @dlh @dmsnell @donmhico @drysand @ekla @ellatrix @emptyopssphere @fabiankaegy @fakhriaz @gaisma22 @gaurangsondagar @gauri87 @gautammkgarg @gulamdastgir04 @hbhalodia @hmbashar @huzaifaalmesbah @iamadisingh @ibrahimriaz @im3dabasia1 @immeet94 @jabir20 @jadavsanjay @jarodortegaaraya @jigarkahar @joedolson @jonsurrell @joppuyo @josephscott @jsmansart @juanfra @kelvinballoo @khokansardar @khushi1501 @khushdoms @lakshyajeet @louischan @mabfahad @madhavishah01 @mai21 @manhar @manhphucofficial @manishxdp @maulikmakwana2008 @maxschmeling @mcsf @mdibrahimk48 @mindctrl @mirmpro @mokshasharmila13 @monzuralam @mosescursor @navi161 @nilambar @nimeshatxecurify @niravsherasiya7707 @noruzzaman @ocean90 @olmostblue @opurockey @ozgursar @palak678 @pavanpatil1 @pbiron @peterwilsoncc @phpbits @pmbaldha @poena @pooja1210 @poojapadamad @pratiklondhe @pratiknawkar94 @r1k0 @rahultank @ramonopoly @ravichudasama01 @rcorrales @rinkalpagdar @rishavdutta @rollybueno @ronya4927 @sabernhardt @sainathpoojary @sajib1223 @sajjad67 @sandeepdahiya @shailu25 @shekharnwagh @shibleemehdi @showravhasan @siliconforks @SirLouen @soyebsalar01 @sourabhjain @spiraltee @sukhendu2002 @suhan2411 @swissspidy @tobiasbg @tusharaddweb @tusharbharti @ugyensupport @valentingrenier @vgnavada @westonruter @wildworks @xwolf @youknowriad @yusufmudagal

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

Get Involved — Help Test WordPress 7.1

The WordPress 7.1 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

The quickest way is Test Core Tickets with Playground — test directly in your browser with zero setup. For applying .patch/.diff files or running test suites, follow the Set Up a Testing Environment guide to get a local Docker-based install running. To test the 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, see the Test Gutenberg guide.

2. Find Something to Test

There are tickets and PRs waiting for testers right now:

– Core Trac — Needs Testing — All open Core tickets needing testing, across all milestones
– Gutenberg Issues — Needs Testing — Open 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 that need reproduction or verification
– Gutenberg PRs — Needs Testing — Pull requests that need someone to verify the fix works

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

– #core-test 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/ — The main hub for testing discussions, questions, and coordination
– Test Team Handbook — Everything you need to know about testing WordPress
– Contributor Day — Join a 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/ at a 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. near you, or participate remotely

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

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

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

Moses Cursor Ssebunya 1:34 pm on July 2, 2026
Tags: , , ,   

Month in Test: July 02, 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 weeks, a good number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.

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

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

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

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

a. Patch Testing 🩹

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

The following tickets (13) 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 (135) 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 (18) 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 (0) 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 🎉

– 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 @nikunj8866 for peer reviewing this post

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

Nikunj Hatkar 1:25 pm on June 22, 2026
Tags: , ,   

Test Chat Summary: June 18th, 2026

On Thursday, 18 June 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 @huzaifaalmesbah @r1k0 @Jadavsanjay @pavanpatil1 @juanmaguitar @mosescursor

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

  1. Weekly Testing Digest failed
    • Reported that this week’s Weekly Testing Digest workflow failed to run, sharing the failed run for reference and noting a recently merged PR #172 that touched the file, in case it was related.
    • @huzaifaalmesbah suggested creating 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 to track and investigate the failure, noting the workflow may need to install the required Playwright browsers before running the digest script.
    • @ozgursar shared the error message, which indicated the Playwright Chromium executable was missing on the runner (chrome-headless-shell not found).
    • @r1k0 felt the merged PR was not the cause and suspected the cached browser instead, agreeing with @ozgursar that updating the Playwright version might resolve it. He offered to investigate in depth and noted the workflow should be updated to prevent this from recurring.
    • @nikunj8866 created issue #177 to track the failure, inviting further comments there.
  2. Recognize WordPress 7.0 Test Contributors – Badge Awards & Blog Post
    • @nikunj8866 noted this was discussed in the last voice chat, but with the 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. event fewer members could join, so it was revisited. He shared his thoughts on issue #174 and invited input.
    • @huzaifaalmesbah suggested not waiting too long on the blog post since the 7.1 release squad has already been announced – publishing it if everyone agrees, or otherwise revisiting a similar recognition effort during the 7.1 release cycle.
    • @nikunj8866 agreed and asked @mosescursor for his opinion on the blog post.
    • @mosescursor confirmed he would take a look.
  3. Proposal: Building a Test Chat and Bug Scrub Facilitator Plugin
    • @r1k0 tested 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. and found it really great.
    • @nikunj8866 shared his view that a plugin is a better approach than a website, as it keeps everything within the WordPress ecosystem and is easier for the team to maintain and use. He suggested documenting the plugin’s details on the Test Chat Moderator Guide handbook page, and adding a live preview link so clicking a button opens WordPress Playground with the plugin already installed for instant testing. He invited everyone to share their thoughts on issue #165.
  4. Provide structured guidance for Core Trac ticket reports
    • @nikunj8866 suggested that issue #116 might be better handled by 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 – either by raising it in #meta or by creating a ticket in the Meta Trac.
    • @r1k0 agreed and offered to open it in the Meta TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/., with the GitHub issue closed as not planned.
  5. Proposal: Restructure Test Handbook to Support Multiple Testing Domains

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 1:00 pm on June 9, 2026
Tags: ,   

Test Team Voice Chat Summary:: 4th June, 2026

Voice Chat notes: 6/4/26 in #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/ AI took notes for this huddle from 1:02:57 AM – 1:35:04 AM GMT+10. Test team discussed PR reviews, a facilitator 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. proposal, contributor badge criteria, and upcoming WordPress ecosystem announcements and testing opportunities. View huddle in channel

Attendees

@nikunj8866, @ozgursar, @Mohammed Kateregga, @SAndrew, and @Kamran Abdul Aziz

🌟 Summary

  • Testing Digest PR: Patch Version Milestones
    • @nikunj8866 and @ozgursar lack familiarity with the workflow automation involved in this PR. [10:07] [10:15]
    • @nikunj8866 identified Enrico and Junema as better suited to review the PR due to their involvement with the automated workflow. [10:28]
    • @ozgursar explained the workflow uses 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/ Actions to scrape test results, summarize them, and push to Slack. [10:29] [10:50]
  • Chat and Bug Scrub Facilitator Plugin
    • @nikunj8866 reviewed the plugin and agrees it is the best option compared to a separate web page. [11:31] [11:39]
    • @ozgursar stored messages in a JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. file rather than hardcoding in 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 to allow easy editing and customization. [11:49]
    • Copy-pasting plugin content to Slack loses formatting (backticks for usernames); manual editing is required to restore formatting. [12:15] [12:47]
    • @ozgursar already linked a WordPress Playground preview in the GitHub issue for direct testing without hosting. [13:59] [14:21]
    • @nikunj8866 suggested adding plugin details to the chat moderator guide handbook page. [13:28]
  • WordPress 7.0 Test Contributors Badge Awards
    • @nikunj8866 reviewed the proposal and confirmed the criteria requirement: contributors must submit 5 test reports to qualify. [17:37] [18:01]
    • Badge assignment cannot be automated; the system only allows accepting or rejecting requests, not directly adding badges to profiles. [18:10] [18:42]
    • @ozgursar suggested announcing the 7.0 test contributors and allowing people to request badges themselves after seeing the announcement. [19:15]
    • @nikunj8866 will review a draft blog post and discuss it with Moses before finalizing. [19:31]

🗣️ 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.

#test-chat-summary

Nikunj Hatkar 1:20 pm on May 25, 2026
Tags: ,   

Test Chat Summary: May 21st, 2026

On Thursday, 21 May 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 @huzaifaalmesbah @ozgursar @r1k0 @juanmaguitar @mabfahad @pavanpatil1 @mosescursor @andrewssanya (sync) @Jadavsanjay (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

Review the current handbook PRs before publishing

  1. Update reproduction and patch testing report templates
    • @ozgursar noted that the Test Reports plugin had already been updated 1 day ago, with the changelog confirming the change aligned with the handbook PR.
    • @huzaifaalmesbah confirmed 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. now reflects the new Bug Reproduction and Patch Testing templates.
    • Special thanks to @afragen for the quick turnaround on the plugin update.
    • Merged the PR after no concerns were raised.
  2. Create patch testing scrub guide
    • @ozgursar confirmed it looked good.
    • Merged this PR as well after review.

Proposed new handbook pages

  1. Proposal: Building a Test Chat and Bug Scrub Facilitator Plugin
    • @ozgursar proposed building a WordPress plugin to help facilitate Test Chats and Bug Scrubs by replacing boilerplate text placeholders.
    • @nikunj8866 suggested that 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 template could be a simpler and more maintainable alternative to a plugin – paired with a sample filled-out issue on the Chat Moderator handbook page so facilitators know what good looks like.
    • @juanmaguitar floated the idea of exploring an AI Agent skill to handle this workflow, and @nikunj8866 asked that this idea be added to the GitHub issue to keep all proposals in one place.
    • @mosescursor expressed support for the GitHub template approach.
    • @ozgursar agreed the GitHub template serves a similar purpose and offered to build a prototype for the Scrub only during upcoming free days, with the goal of brainstorming further possibilities and finding something easier to maintain long-term.
    • @nikunj8866 welcomed the prototype idea and invited everyone to share feedback either 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/ or on the GitHub issue.

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