Highlighted Posts

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

Test Team Voice Chat Agenda: 2nd April, 2026

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

Agenda

Leave a Comment

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

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

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

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

Test Chat Summary: 26th March, 2026

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

1. Attendance

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

2. Volunteer

This week’s facilitator was @r1k0

This week’s note-taker was @r1k0

3. Test Team Discussions

Review the current handbook PRs before publishing

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

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

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

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

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

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

The team agreed that the most appropriate location would be under “Get set up testing”, with the page to be added there for now as the last item.
@r1k0 requested that the conversation be continued on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ to discuss the page creation and placement further.

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

@mosescursor reviewed the PR and provided feedback.

@ozgursar Reviewed and helped co-author the PR.

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

Proposed new handbook pages

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

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

@nikunj8866 agreed that this page is necessary.

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

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

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

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

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

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

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

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

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

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

4. Open Floor

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

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

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

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

#test-chat-summary

Test Team Chat Agenda: 26th March, 2026

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

Agenda

Leave a Comment

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

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

#core-test, #test-chat-agenda

X-post: Call for Testing: Community AI Connector Plugins

X-comment from +make.wordpress.org/ai: Comment on Call for Testing: Community AI Connector Plugins

X-post: Test Team Update: 24 March, 2026

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

Core Test Team at WCAsia 2026: Contributor Day

Hello WordPress enthusiasts 👋

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

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

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

  • 8:00 AM – Registration Open and Networking Time
  • 9:00 AM – Opening Remarks
  • 9:30 AM – Contributing to WordPress / WordPress 7.0 Release Session / Workshop / Open-Source Library
  • 11:00 AM – WordPress Release Panel Discussions and Open Floor
  • 11:45 AM – WordPress Release Ceremony 🎉
  • 12:00 PM – Long Break / Networking
  • 1:45 PM – Family Photo
  • 2:00 PM – Contributing to WordPress / Workshop / Open-Source Library
  • 4:30 PM – Closing Remarks
  • 5:00 PM – Contributor Day Wrap Up

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

👩🏻‍💻 Meet the Test Team Table Leads

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

In-Person Table Leads:

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

🎯 Core Test Team Goals

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

  • Onboard New Contributors: Provide guidance and mentorship to newcomers eager to join the Core Test Team.
  • Celebrate and Explore WordPress 7.0: WordPress 7.0 is launching live on Contributor Day! Join us in witnessing the release ceremony and explore the new features firsthand.
  • Help Test WordPress 7.0: Once the release goes live, dive in and help the community by testing the new release, exploring new features, and reporting any issues you find.
  • Help with tickets that need testing (Core):
  • Help with tickets that need testing (GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/):
  • Test bugs or features and report new issues.
  • Improve Documentation: Enhance the clarity and comprehensiveness of testing guidelines.

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

🌐 Collaboration and Community

Contributor Day at WCAsia 2026 isn’t just about work – it’s also about building connections and fostering community spirit. With WordPress 7.0 launching live during the day, there’ll be a fantastic energy in the room as the community comes together to celebrate this milestone. The afternoon session is the perfect opportunity to put the brand-new release through its paces and help make WordPress even better from day one.

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

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

🔗 Helpful Resources

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

👀 Looking Ahead

As we gear up for this landmark Contributor Day, we’re excited about the incredible energy that will fill the room in Mumbai. Being present for a live WordPress 7.0 release is a once-in-a-community-moment – and your contributions, whether big or small, help make WordPress better for everyone. 💪

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

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

#wcasia2026, #core-test

It’s time to test real-time collaboration!

Iteration issue: https://github.com/WordPress/gutenberg/issues/74549

Have you been waiting to collaborate in WordPress posts the way you do in Google Docs? Here’s your chance!

Real-time collaboration is the crowning feature of the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ Project phase 3, and this is the first iteration to land in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. You can call it RTC for short.

But before it can get there, RTC needs you! (And your friends!) Every part of this groundbreaking functionality, from front-end usability to literal php functions, plus database calls, APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. endpoints, and more, needs to run this first implementation through its paces.

In short, please ride this hard. Try to break everything! That’s how the folks who’ve been working hard on this for years will know it’s good enough to be in Core.

Testing steps:

  • Install WordPress 7.0 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 on a server that somebody else can reach. 
  • This should probably be a new installation. maybe on a local network or on a staging server, or something in between—not a production server, but also not a local installLocal Install A local install of WordPress is a way to create a staging environment by installing a LAMP or LEMP stack on your local computer. on a single machine.
  • In 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., navigate to Settings > Writing and toggle on “Enable real-time collaboration.
  • Open a post for editing. Start with a regular post, of course, but remember that pages are also posts, and custom post types are posts too! There are some exceptions, which you’ll find below. 
  • Invite a friend or colleague (or two or ten!) to edit the same post.
    • Consider joining a video call and sharing your screens so you can each see both experiences.
    • Or, collaborate with yourself! To do that, open your install in a separate tab and log in as someone else. See if you can edit as both people!
    • Another option: open your site on two machines on the same network.
  • If you have some, use real content—real text and images, other data sources and other media. See if you can use your usual workflows.

What to expect

  • Real-time collaboration only works when you’re editing posts in 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. It won’t function on other admin screens.
  • Classic post 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. boxes do not sync. Using these boxes still works, but your collaborators will not see updates in real time. They might even overwrite each other’s changes.
    • Without looking at the code, it’s not always obvious whether a post meta box is Classic (persisted using a save_post hook) or modern (integrated with the Gutenberg data store). Many plugins still use Classic post meta boxes.
  • Most blocks are compatible. Blocks are synced via their attributes, which means that most blocks support real-time collaboration by default. Some blocks might use local state when working with user input, which can result in issues during real-time collaboration.
  • Plugins that integrate with the block editor might have issues. Behavior with plugins is some of the most important feedback you can give. 
  • Collaborator cursors disappear in the Show Template view.
  • Collaborating on the same block can have issues. Please test it anyway, but expect quirkiness around cursor placement. Your feedback may well speed up the fix!
  • Syncing happens over HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. polling, so it’s not instant. It could feel laggy sometimes—please report this! As well, if it feels much smoother at some points than at others, please report that. Performance will directly affect how the community takes to RTC long-term.

What to notice

About overall functionality:

  • Did real-time collaboration work the whole time? 
  • Did you get disconnected? Did it ever feel unresponsive to the point that it interrupted your work?
  • Did you lose any content? How about duplication?

In real-life workflows, could you collaborate:

  • On custom blocks?
  • Inside a plugin’s 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.?
  • In the site editor?
  • On a large document?
  • If you added more than one user?

How did RTC do on 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)? Did it work:

  • Only  using the keyboard?
  • With a screen reader?
  • On a mobile device?

Thank you!

Please report your findings to the fine folks at #feature-realtime-collaboration on Make 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 directly to the authors of this post. If you’re comfortable with 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/, the best place to report would be in comments on the tracking issue, #52593.

One more thing: RTC is getting its own table.

That hasn’t merged yet, but if you want to follow its progress, start with the discussion on the ticket at https://core.trac.wordpress.org/ticket/64696#comment:44 and happy testing!

Props to @ankit-k-gupta, @maxschmeling, @czarate, and @annezazu for peer review and collaboration.

#7-0, #core-test, #gutenberg

X-post: Test Team Update: 10 March, 2026

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

X-post: Call For Feedback: Increasing Value of Release Party Testing Phase

X-comment from +make.wordpress.org/core: Comment on Call For Feedback: Increasing Value of Release Party Testing Phase

Month in Test: March 3, 2026

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

Table of Contents

Calls for Testing 📣

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

Test Handbook 📘

Merging of Test Handbook in GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/

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

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

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

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

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

a. Patch Testing 🩹

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

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

b. Bug Reproduction

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

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

c. Test Team Issues

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

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

2. GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ Testing

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

a. Gutenberg Bug Reproduction Testing

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

b. Gutenberg Patch Testing

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

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

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉

  • none this Month

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

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

Upcoming Meetings 🗓

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

Current 2026 Schedule:

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

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