The Test Team helps manage testing and triage across the WordPress ecosystem. They focus on user testing of the editing experience and WordPress dashboard, replicating and documenting bug reports, and supporting a culture of review and triage across the project.
Please drop by any time in SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ with questions or to help out.
🎧 Huddle Notes: 11/5/26 in #core-test. AI took notes for this huddle from 1:01:34 AM – 1:49:43 AM GMT+10. Test Team discussed workflow failures, badge criteria proposals, documentation PRs, and new automation tooling; addressed stalled contributions requiring team takeover.
@huzaifaalmesbah identified TracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. scrape timeout issue blocking the digest workflow. [5:59]
@ozgursar noted contributor Rajoul is blocked; team discussed testing approach using feature repo with real SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ webhook. [7:41] [7:58]
@huzaifaalmesbah proposed MCP (Model Context Protocol) as best solution to bypass verification; already tested locally on separate branch. [10:46] [12:37]
@jns141191 agreed badges should be awarded after release completion per handbook rules. [15:48]
@ozgursar clarified process: volunteer call precedes release, CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team selects leads, then Test Team awards badges post-release. [16:12]
@jns141191 confirmed badges require continuous contribution; inactivity over three months may trigger removal, but emeritus badges available for long-term members.
@r1k0 noted removal is discretionary and requires extended inactivity (year+), not just three months. [20:54]
Contributor Toolkit Documentation PR Review
@ozgursar tested desktop application; it auto-builds environment but lacks documentation of test steps; platform variations (Mac/Linux) untested. [26:58] [28:01]
@ozgursar suggested pinging Ryan (maintainer) for review; team can pre-review using existing handbook contributor toolkit documentation. [29:24] [30:38]
Team agreed to review PR and provide feedback before Ryan’s final approval. [31:31]
New Trac Need-Testing Announcer
Merged PR #8157 adds automatic Slack announcer for tickets marked “needs-testing,” mirroring GutenbergGutenbergThe 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/ announcer functionality.
Manuel pioneered and implemented the announcer; @huzaifaalmesbah credited Manuel’s behind-scenes contributions to Test Team. [35:37] [36:24]
@ozgursar clarified: announcer automatically surfaces tickets to Slack without manual action once keyword applied. [37:34]
Team to report any announcer issues to Manuel via Slack mention for fixes. [38:07]
Open Floor
Stalled Contributor PRs Requiring Takeover
Two PRs opened by inactive contributor: “Update Contributor DayContributor DayContributor 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/ getting started guide” and “Fix typos in Test Handbook documentation.”
@huzaifaalmesbah noted both are minor manual changes suitable for team takeover and merge. [41:12] [41:52]
@ozgursar volunteered to review and apply changes to both PRs. [42:20]
Personal announcement
@noruzzaman announced birth of child; apologized for unavailability on 7.2 personal channel due to hospital time. [33:19] [33:53]
The Presence APIAPIAn 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.feature pluginFeature PluginA plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins team is preparing for a proposal to merge into WordPress CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. as the foundation for real-time awareness and modernized post locking.
We invite the community and the Make/Test team to test the admin interfaces and real-time interactions across typical admin workflows. Feedback is open through November 23, 2026.
What is Being Tested?
Real-Time Awareness: Live presence indicators across the admin toolbar, posts list, and user screens.
Modernized Post Locks: Post locks look and behave identically to standard WordPress core post locking, but their storage has moved off the _edit_lock post field and into the dedicated wp_presence table (#548).
Build Version: The Playground blueprints test the latest preview-main build (built from the main branch).
How to Test
You can test directly in your browser using WordPress Playground without any local environment setup:
Option A: Interactive Testing with Simulated Collaborators (Recommended)
This instance runs the companion presence-scenes tool, which simulates real-time virtual users editing posts and navigating the admin:
(Note: Because Playground stores site state locally in your browser storage, opening two separate browser windows or an incognito tab creates independent Playground sites. To test multi-user actions, please use the simulated collaborators in Option A or the Demo bar in Option B. Additionally, seeded demo users time out after ~2.5 minutes of inactivity; if this happens, simply relaunch the blueprint link to reseed).
Guided Test Tasks
Task 1: Admin Bar Real-Time Presence
Use Option A (Simulated Collaborators).
Open wp-admin and find the faces and “N online” count next to Howdy in the toolbar.
Observe the counter updating as simulated collaborators move across screens.
Hover or use keyboard navigation (Tab) to open the presence menu.
What to verify:
The faces and menu show other people (not you), and the “N online” count includes you.
User avatars and names are legible, tooltips render correctly, and keyboard focus works properly.
Admin bar presence menu on desktop showing active collaborators.
Task 2: Posts List & “Editors” Column
Use Option A with the “Editing together” scene (/wp-admin/edit.php?presence_scene=editing-together).
A few seconds after the scene starts, reload Posts > All Posts.
Find Launch checklist, the post the collaborators are editing.
What to verify:
The Editors column shows an avatarAvatarAn avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. stack indicating active editors.
Hovering or navigating into the row with a keyboard reveals collaborator names.
On smaller screens (or responsive mobile view), avatars adjust without causing horizontal overflow.
Editors column showing active collaborator avatar stack in the Posts list.
(Note: The simulated scene runs for under a minute. When the scene completes, it automatically cleans up its simulated users and deletes the “Launch checklist” post. Testers should act within this window, or replay the scene at any time by revisiting /wp-admin/edit.php?presence_scene=editing-together.)
Task 3: Post Locking and Takeover
Use Option A with the “Editing together” scene.
In Posts > All Posts, click to edit a post that another collaborator is currently editing.
Observe the post lock dialog.
Click Take over.
What to verify:
The lock dialog indicates that another user is currently editing the post.
Taking over closes the dialog and lets you edit the post.
(Note: If the scene finishes before you take over, the post will be deleted. Simply refresh /wp-admin/edit.php?presence_scene=editing-together to replay).
Task 4: Stale Screen Notification
Use Option B (Demo Data).
Navigate to Settings > General.
In the Demo bar at the top, click a Save as {name} button.
What to verify:
A yellow stale-screen notification appears indicating that someone else has saved changes to this screen.
When dismissing the notice, keyboard focus smoothly moves to the screen heading.
(Note: The stale-screen notice is designed for individual edit screens and settings pages, not the main Posts list).
What to Check
AccessibilityAccessibilityAccessibility (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): Can you navigate and operate all presence indicators using only a keyboard?
Responsiveness: Do views on phones or tablets display cleanly without broken layouts? (See #830 for reference phone layouts).
Usability: Are presence indicators informative without being distracting?
Phone admin bar: compact user icon and online count (<600px).Phone touch menu: expands on tap to display collaborator names.
Known Issues
The current open issues list is tracked on GitHub Issues.
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.
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:
Merging of Test Handbook in GithubGitHubGitHub 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
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 CoreCoreCore 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 (11) 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:
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 (117) 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:
2. GutenbergGutenbergThe 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
The following tickets (7) have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.
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:
Note-taker and facilitator selection for the next meeting We encourage all members to contribute to the team chat, and we now welcome note-takers and Facilitators. This is a great time to get involved in the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. test team. Have you recently joined, and you don’t know where to go? Start here (No Skills Required)
We are looking for a volunteer facilitator and note-taker for the next session. PingPingThe 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.” us #core-test to volunteer
Finally, a look at the new TracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. need-testing announcer (after merging of #8157).
Open Floor
Got a topic? Add in comments below, or bring it up live during the chat.
You must be logged in to post a comment.