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.
As part of the upcoming WordPress 7.1 release, we’re working on responsive styling – the ability to style blocks differently for tablet and mobile, directly from the editor. PR #75121 unifies the resizable editor with the device-preview switcher, which is the groundwork this feature builds on, and we’d love your help testing it.
More testing is needed to make sure it’s reliable and intuitive before it ships.
What is responsive styling?
Until now, a style you set on a blockBlockBlock 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. – a font size, some spacing – applied the same way on every screen. Responsive styling lets you change a value just for tablet or just for mobile, without writing any custom CSSCSSCSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site..
A few real examples:
A large heading on desktop that becomes smaller on mobile.
Generous padding on desktop that tightens up on a phone.
A different text color on the tablet than on the desktop.
To make these changes, first turn on Responsive editing from the device-preview dropdown – then switch the device view to Tablet or Mobile and edit the value while that view is active. The change is saved only for that breakpoint.
Why this matters
Let’s you match a design across screen sizes without leaving the editor or hand-writing media queries.
Keeps responsive tweaks, visual, and previewable – what you see is what visitors get.
Moves WordPress toward fuller per-breakpoint design control in the editor.
How to test
The easiest way to test is WordPress Playground – no setup, nothing to install. This loads a fresh site with the latest 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/, which includes the responsive styling work plus any fixes that have landed since.
The link logs you in as admin and opens a fresh post, ready to test. Building the PR can take a minute on first load, so give it a moment.
Tip: The device view switcher is the Desktop / Tablet / Mobile dropdown in the editor’s top toolbar. Switching it is how you tell WordPress which breakpoint you’re looking at. With this PR, you can also drag the resize handles at the edge of the canvas to change the width.
Key changes to observe
The device-preview dropdown and the resizable editor now work together: picking Tablet or Mobile sets the canvas width, and dragging the resize handles updates the device view to match.
The dropdown has a new Responsive editing option. When it’s on, style changes you make apply to the current viewport (Tablet or Mobile) instead of Desktop.
When Responsive editing is on, and you select a block on Tablet or Mobile, a viewport badge appears in the block inspector showing which device you’re editing. No badge is shown on the desktop, since edits there apply everywhere.
Per-viewport edits are preserved and shown per device; turning Responsive editing off resets the editing state to default, and the badge disappears.
Test steps
You don’t need to follow all of these – pick what you have time for, and note anything that feels broken or confusing.
Scenario 1 – Resize handles and device view together (Post editor)
In the post editor, open the device dropdown and switch to Tablet (resize handles appear on the canvas edges).
Drag a handle inward and outward and watch the canvas width change.
Drag a handle all the way out to its widest – the handles should disappear, and you should land back in Desktop view.
Confirm the dropdown and the handles always agree on which view you’re in.
Note: In Desktop view, the handles may not show at first if there’s no spare space beside the canvas – use the dropdown to switch to Tablet/Mobile first. This is expected.
Scenario 2 – Pattern editor and Navigation editor
Edit or create a pattern (Appearance → Patterns, or via the site editor).
Here, the resize handles are always visible. Drag them and also use the device dropdown.
Confirm the two stay in sync and the canvas resizes smoothly.
Repeat the same check in the Navigation editor (Appearance → Editor → Navigation), where the handles are also always visible.
This change touches all four editors – Post, Template / Site (Appearance → Editor → Templates), Pattern, and Navigation – so testing across more than one is especially valuable.
Scenario 3 – Responsive editing (the main one)
Open the device-preview dropdown and turn on Responsive editing.
Select a block that has style options (e.g., a Heading). (On Desktop, no viewport badge is shown – this is intended.)
Switch the device preview to Tablet or Mobile – or drag the canvas to that width. A viewport badge now appears in the block inspector (right sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.) showing which device you’re editing.
Change a style (for example, a smaller font size). Confirm the change applies only to that viewport, not to Desktop.
Switch back to Desktop and confirm your per-viewport edit is preserved and the Desktop value is unchanged.
Turn Responsive editing off and confirm the editing state resets to default, and the badge disappears.
Also worth trying (quick real-world checks):
Save and reload the editor – your per-viewport edits should still be there.
Try it on a couple of different blocks (Group, Button, Image) and different properties (spacing, colors), not just font size.
Set both Tablet and Mobile differently on the same block and confirm each is remembered.
Undo/redo a per-viewport edit and confirm it behaves sensibly.
Scenario 4 – Hidden-on-device blocks respond to canvas resize
Block visibility itself has already shipped in Gutenberg. What’s new in this PR is that resizing the canvas (not just the device dropdown) now triggers it.
Add a paragraph and set it to be hidden on Tablet using the block’s visibility option.
Drag the resize handles into tablet width. The block should hide.
Drag back out to the desktop width. The block should reappear.
Confirm the device dropdown set to Tablet hides it too, exactly as before.
Always check the front end
After any responsive edit, verify it in both modes:
Preview – use the editor’s Preview (the “View” / preview option) to open the page before publishing.
Saved/published – Save, then open the live URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org.
In each mode, resize your browser from wide to narrow – or use your browser’s device/responsive view – through desktop, tablet, and mobile widths. Each width should show the style you set for it (e.g. the smaller font on mobile, the different color on tablet), and both Preview and the saved front end should match what you saw in the editor at the same width.
What to expect
This is active development, so expect a few rough edges, and the UIUIUI 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. may still change. A couple of things that are known or by design:
Resize handles in Desktop view (post/template editor): they may not appear at first because there isn’t enough space beside the canvas. Switch to Tablet or Mobile via the dropdown first. A follow-up is planned – see #71210.
Responsive editing is desktop-first: a value you set on Desktop carries down to Tablet and Mobile unless you override it at that smaller viewport. So seeing the Desktop style on mobile (until you change it) is expected.
Only styles set in the block inspector (right sidebar) – font size, colors, spacing, etc. – apply per viewport. Block toolbar controls like alignment apply to all devices.
For pluginPluginA 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 theme developers
If your plugin or theme interacts with the editor canvas, please test it against this build – the underlying device/canvas model has changed:
Code using getDeviceType() / setDeviceType() should keep working. getDeviceType() now derives the device from the canvas width, and setDeviceType() converts a device to a width.
useResizeCanvas() is now deprecated and a no-op. If you rely on it, please tell us your use case.
Responsive styles work out of the box for custom blocks that use block supports (color, typography, border, layout, dimensions), so custom block authors can test on their own blocks too (Note: if a block implements custom controls instead of block supports, responsive styles won’t apply to those).
Sharing your Feedback
There are a few ways to share what you find:
General feedback / UXUXUX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. impressions: comment on this post – it’s the best place for overall impressions and questions.
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 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
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 (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:
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:
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 (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.
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 🎉
Here is the agenda for the upcoming Test Team Voice Chat scheduled for Thursday, 7th May, 2026 at 15:00 UTC which is held in the #core-test Slack channel. Lurkers welcome!
Agenda
Attendance
Attendance check in with the wp.org username. Posted in the chat section
Note-taker and facilitator selection for the next meeting We encourage all members to contribute to the meeting, and we now welcome Note Takers and Facilitators. Anyone can hold a Voice Chat. 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)
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:
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 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
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 (2) 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 (134) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, then provide a bug reproduction report:
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 (9) 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 (3) 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:
🚨 There will be regular #core-test meetings. Weekly team meetings are now alternating every Thursday at 15:00 UTC as per schedule. Please mark your calendars.
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 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/ Project phase 3, and this is the first iteration to land in CoreCoreCore 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, 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. 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 BetaBetaA 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 InstallA 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 pluginPluginA 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 blockBlockBlock 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 metaMetaMeta 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 HTTPHTTPHTTP 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 UIUIUI 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 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)? 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 SlackSlackSlack 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 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/, the best place to report would be in comments on the tracking issue, #52593.
Hello and welcome to the 1st 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:
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 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
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 (7) 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 (143) 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 (2) 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:
Hello and welcome to another edition of Week 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:
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 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
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 (2) 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 (169) 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 (1) 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 (2) 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:
Hello and welcome to another edition of Week 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:
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 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
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 (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:
No tickets this week
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 (191) 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 (0) 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.
Nothing this week
b. Gutenberg Patch Testing
All contributors (not just developers) who can set up a local testing environment. Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.
The following tickets have been reviewed, and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:
None this week
Profile Badge Awards 🎉
Congratulations to the recipients of the Test Contributor Badge 🎉
Happy New Year 2026! To more wins and celebrations in our team and more
Hello and welcome to another edition of Week 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:
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 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
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 (5) 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 (202) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, the 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 (0) 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.
Nothing this week
b. Gutenberg Patch Testing
All contributors (not just developers) who can set up a local testing environment. Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.
The following tickets have been reviewed, and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:
None this week
Profile Badge Awards 🎉
Congratulations to the recipients of the Test Contributor Badge 🎉
Meeting started by explaining Note takers and Facilitators so people can take up the roles.
Note takers are simply people who summarize the happening of the Test Chat and they always publish a test Chat summary like this one here.
Facilitators are simply people that chair or facilitate a test team chat. These follow the agenda that is proposed and ensure that every one gets a voice. A sample Meeting is like the one held here.
These 2 can be done by the same person in the same instant however we encourage multiple people to do it to increase on the proof reading and collaboration
Update on Test Handbook: New pages for Feature & Enhancement Testing (#90), E2E Testing (#91), and Patch Testing Scrubs (#92) are available; contributors can update content via 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/ issues.
@sirlouen got to a conclusion that currently we don’t have enough resources to have the wheel moving
all the areas mentioned above require a good thought and a suggestion to expand the team was brought up.
Previously, mentorship was insufficient so now a full training was advised. A program in the test team that will bring in Champions
A call for as many people as possible was made. People that will be committed to the program and see it through
@nikunj8866 sighted it as a great learning opportunity for anyone who wants to become a future Test Team representative.
@sirlouen added that it won’t only make team reps but also Power Members.
@sirlouen will pause current Handbook activity in preparation for the program in the next 2 weeks. Announcement made here highlighting the requirements to join and all the information about the program.
4. Open Floor
We have introduced a bot that informs of new 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/ issues coming for testing. This posts directly in the slackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel
@sirlouen recommended adding an emoji like this if you are going to be doing the testing report.
This helps for quick assignment of tasks and getting them cleared quickly.
Here people get a chance to know the tests required and even do them without having to wait for a Patch-testing session.
Infact this could also end the patch testing sessions when the new training is implemented
We usually have 2 meetings held every week. This is the last test-chat meeting for this year and Tomorrow’s patch testing session will be the last for this year.
if you are going to be doing the testing report.
You must be logged in to post a comment.