Tag Archives: core-test

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

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

Nikunj Hatkar 4:19 am on July 3, 2026
Tags: , , core-test, ,   

Call for Testing: Responsive Styling

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 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. – 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 CSSCSS CSS 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 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/, which includes the responsive styling work plus any fixes that have landed since.

Test responsive styling in Playground

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)

  1. In the post editor, open the device dropdown and switch to Tablet (resize handles appear on the canvas edges).
  2. Drag a handle inward and outward and watch the canvas width change.
  3. Drag a handle all the way out to its widest – the handles should disappear, and you should land back in Desktop view.
  4. 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

  1. Edit or create a pattern (Appearance → Patterns, or via the site editor).
  2. Here, the resize handles are always visible. Drag them and also use the device dropdown.
  3. Confirm the two stay in sync and the canvas resizes smoothly.
  4. 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)

  1. Open the device-preview dropdown and turn on Responsive editing.
  2. Select a block that has style options (e.g., a Heading). (On Desktop, no viewport badge is shown – this is intended.)
  3. 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 sidebarSidebar A 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.
  4. Change a style (for example, a smaller font size). Confirm the change applies only to that viewport, not to Desktop.
  5. Switch back to Desktop and confirm your per-viewport edit is preserved and the Desktop value is unchanged.
  6. 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.

  1. Add a paragraph and set it to be hidden on Tablet using the block’s visibility option.
  2. Drag the resize handles into tablet width. The block should hide.
  3. Drag back out to the desktop width. The block should reappear.
  4. 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 URLURL A 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 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. 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 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 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 / UXUX UX 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.
  • Bugs and regressions: open a Gutenberg issue and reference PR #75121.
  • Not sure whether it’s a bug? Ask in the #core-test channel on the WordPress 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/.

We’d love to know, for example:

Specifics:

  • Was it clear how to turn on Responsive editing and which viewport you were editing?
  • Did the viewport badge correctly follow the device as you switched?
  • Did a per-viewport style edit stay on that viewport only, and survive a save and reload?
  • Did the device dropdown and the resize handles always agree on the current view?
  • Did resizing feel smooth, or did handles get stuck or disappear unexpectedly?
  • Did the editor preview match the front end at each width?
  • Did anything feel slower, confusing, or broken?

The bigger picture:

  • How intuitive did responsive styling feel overall – were you able to do what you wanted without guidance?
  • Does this solve a real problem for you? Would you use it in an actual project?
  • Anything about the overall approach that felt right, or that you’d design differently?

When reporting something, a short step-by-step with a screenshot or screen recording helps a lot. To make a report actionable, please include:

  • The editor you used (Post, Template / Site, Pattern, or Navigation).
  • Your browser and OS, and whether it was a touch device.
  • The Gutenberg / WordPress version or PR build.
  • The active theme – especially block themes with custom breakpoints.

Props to @huzaifaalmesbah, @jeffpaul, @talldanwp, @isabel_brison, and @annezazu for review and feedback on this post.

#7-1, #call-for-testing, #core-test, #full-site-editing, #gutenberg

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

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: core-test, ,   

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 18, 2026
Tags: core-test,   

Team Chat Agenda: 18th June, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 18 June 2026, 03:00 PM UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

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

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

#test-chat-agenda

Nikunj Hatkar 1:00 pm on June 9, 2026
Tags: core-test,   

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:33 pm on June 5, 2026
Tags: core-test   

Month in Test: June 05, 2026

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

Table of Contents

  1. Calls for Testing 📣
  2. Test Handbook📘
    1. Merging of Test Handbook in Github
  3. Weekly Testing Roundup 🤠
    1. 1. WordPress Core Testing
      1. a. Patch Testing 🩹
      2. b. Bug Reproduction
      3. c. Test Team Issues
    2. 2. Gutenberg Testing
      1. a. Gutenberg Bug Reproduction Testing
      2. b. Gutenberg Patch Testing
  4. Profile Badge Awards 🎉
  5. Read/Watch/Listen 🔗
  6. Upcoming Meetings 🗓

Calls for Testing 📣

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

Test Handbook 📘

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

For the last few 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 (10) 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 (139) 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 (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.

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 🎉

– 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.

#core-test

Nikunj Hatkar 1:29 pm on June 4, 2026
Tags: core-test,   

Test Team Voice Chat Agenda: 4th June, 2026

Here is the agenda for the upcoming Test Team Voice Chat scheduled for Thursday, 4 June 2026, 03:00 PM UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

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

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

#core-test, #test-chat-agenda

Nikunj Hatkar 10:41 am on June 3, 2026
Tags: #wceu2026, core-test,   

Core Test Team at WCEU 2026: Contributor Day

Hello WordPress enthusiasts 👋

Tomorrow we head to Kraków. The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Team is gearing up for Contributor Day at WordCamp Europe 2026, taking place 4 June 2026 at ICE Kraków – the official kick-off to WCEU.

Testing is one of the most welcoming doors into WordPress: you don’t need to write a line of code to make a real difference, and by the end of the day you’ll have touched software used by over 40% of the web. Whether it’s your first 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/ or your fifteenth, there’s a seat for you at the Test table. Here’s what we’ve got planned and how to make the most of it.

🕰️ Schedule

All times are Central European Summer Time (CEST). Plan to arrive about an hour early to register and settle in.

  • 8:30 – Registration
  • 9:15 – Opening and welcome
  • 10:00 – Contributing to WordPress
  • 12:15 – Group photo
  • 12:30 – Lunch
  • 14:00 – Contributing to WordPress
  • 16:30 – Team summaries and wrap-up

Joining from home? Remote contributors are just as welcome – find us in the #contributor-day and #core-test channels in Make WordPress Slack.

👩🏻‍💻 Meet the Test Team Table Leads

In-Person Table Leads:

Online (Remote) Table Lead

Anukasha will be on the ground in Kraków to welcome you and get you set up, while Nimesh holds down the digital table – coordinating remote contributors and answering questions 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/ throughout the day. Other Test Team regulars will be dropping by in person and online to lend a hand.

🎯 What We’ll Work On

Our focus is meaningful, achievable contributions you can make real progress on in a few focused hours:

  • Onboard new contributors. If you’ve never tested before, this is the place to start. We’ll walk you through your first test, your first triage, and your first reproduction – no prior experience needed.
  • Test core tickets that need eyes. Pick up live work straight from TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.:
  • Test the editor (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/).
  • Help test the new career functionality on 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/. There’s an active call for testing (feedback open through June 25) for the refreshed jobs.wordpress.net and the new career fields on WordPress.org profiles – job history, key accomplishments, and an “open to work” toggle. Try the applying-for-jobs 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., browse candidates on the Jobs site, and leave feedback on the post or by opening an issue on GitHub.
  • Find a bug? File it. A clear, reproducible report on Trac is a genuine contribution in itself.
  • Improve the docs. Help sharpen the Test Team Handbook and testing guides so the next newcomer has an easier path than you did.

Bring whatever skills and curiosity you have – table leads and experienced contributors will help you find the right task. Everyone is welcome.

A gentle reminder: it’s Contributor Day, not Contribution Day. The goal is to find a meaningful way to contribute, not necessarily to land a finished patch by 16:30. Work you start tomorrow might wrap up next week – and that’s exactly how open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. is meant to work.

🌐 Collaboration and Community

Contributor Day isn’t only about the work – it’s about the people. It’s a room full of contributors swapping ideas, helping each other unstick, and celebrating small wins together. For many of us, the connections made across the Test table are what keep us coming back year after year. Come for the testing, stay for the community.

If you’d like to keep contributing after Kraków, the Test Team meets every week in #core-test. You can find the full Test Team meeting schedule and upcoming meetings here: https://make.wordpress.org/meetings/#test. Drop by any time to say hi, ask a question, or just lurk and learn.

🧰 Prepare at Home

A little setup the night before means you can dive straight into the fun stuff when you arrive. Spotty venue wifi is a fact of life, so get ahead of it:

🔗 Helpful Resources

👀 Looking Ahead

Every bug reproduced, every patch tested, and every report filed tomorrow ripples out to millions of sites. That’s the quiet power of testing: it’s unglamorous, it’s essential, and it’s how WordPress stays trustworthy release after release. We can’t wait to see what we build together in Kraków – and in Slack.

Not sure Test is the right fit? The Find Your Team tool can point you somewhere that clicks. But if you like the idea of being the person who catches the problem before a user ever does – you’ve found your table.

See you in Kraków! 💙

Props to @nimeshatxecurify for preparing and reviewing this post, and to @anukasha for the review of this post. 🙌

#wceu2026, #core-test, #wceu

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

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