Moses Cursor Ssebunya 7:20 am on October 13, 2025
Tags: core-test, gutenberg ( 73 ), make.wordpress.org/test ( 2 ), make.wordpress.org/updates ( 224 )

Week in Test: October 13, 2025

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.

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:

Collaboration: add 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.-level comments:
- Help Test WordPress 6.9
- Actively developed for 6.9. See #66377

Call for test table lead for WC Islamabad

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. Islamabad is happening on 18–19 October 2025, with 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/ on the 18th. They’re looking for an online table lead for Testing to guide their local community and they’re open to connecting over Zoom/Google Meet. If anyone from the team is interested, please comment on this post or reply in the channel.

Test Handbook 📘

It’s Time to Review the 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 week, a good amount of test contributors have embarked on the journey of reviewing our new Test Handbook based on Github. We still need more members to join, because we must make sure, that every single page is reviewed at least 2 or 3 times to avoid missing anything. If you want to join us, please write in the #core-test chat 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/, and we will help you get on the process.

Here are the handbook Pull requests and here are the pending tasks for review.

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 skill? 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 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. PHPUnit Tests 🛟

Who? Any QA or 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 developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop for quality and backward compatibility.

The following tickets need PHPUnit tests built to accompany their respective patches:

We had no Unit tests this week

c. 6.9 Related issues need testing

The following 6.9 tickets need testing, those are having patches:

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 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 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:

Nothing to test yet this week

Profile Badge Awards 🎉

No Badges Issues this Week

Read/Watch/Listen 🔗

Gutenberg 21.8RC is now available.
The Test Handbook Overhaul
Notes from the Core Committer meeting at WCUS 2025 are now available.
WordPress 6.9 Release Party Schedule
Bug Scrub Schedule for WordPress 6.9
WordPress 6.9 is planned for December 2, 2025, with BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 beginning October 21

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held for 2025.

2025 Schedule:

Wednesday, 15 October 2025 at 17:00 GMT+3 : <patch-testing-session> in #core-test.
Thursday, 16 October 2025 at 18:00 GMT+3 : <patch-testing-session> in #core-test.

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, #gutenberg, #core

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

#core-test, #gutenberg, #make-wordpress-org-test, #make-wordpress-orgupdates

Manuel Camargo 2:21 pm on October 9, 2025
Tags: core-test

Test Chat Summary: October 8, 2025

On 8 October 2025 at 2PM GMT, <test-chat> started in #core-test facilitated by @sirlouen The agenda can be found here.

1. Attendance

@mosescursor @nikunj8866 @agulbra @dhavalkapadane @fakhriaz @muddassirnasim @passoniate (async) @dilip2615 (async)

2. Volunteer

This week’s note-taker was @sirlouen

3. WordPress Ecosystem Announcements

4. Test Team Announcements

The Test Handbook Overhaul
Remember to check Week in Test Post for weekly updated info

5. Call for Testing

6. Test Team Discussion, Questions, and Blockers

1. Handbook Overhaul—Task Assignments

The meeting began with the launch of the Handbook Overhaul project, focusing on assigning tasks to contributors.
Each participant will be assigned at least one new page to create and two or three pages to review.
The objective is to ensure every single documentation page is properly replicated before the originals are deleted—anything not replicated will be lost.
Tasks for contributors fall into three categories:
- Create: New pages to be created, primarily copied from the originals.
- Review: Existing pages requiring review and verification.
- Discuss: Pages to be discussed in any meeting, like the Archive section.
A second call-out will be made for more volunteers, who will then be assigned tickets.

2. Proposal: Archiving Old Sections

A proposal was presented to create an “Archive” section in the documentation for obsolete content.
The specific example raised was archiving the “FSE Outreach Experiment” page and similar sections not currently useful.

3. Section Review: “Crawl your test site for errors”

A specific section, “Crawl your test site for errors”, was discussed.
The group debated whether this section is still relevant to keep, with some members expressing doubts.
The decision was left open for further review and comments. Removal will be approached in the next meeting unless there are any arguments against it.

7. Closing and Open Floor

@fakhriaz commented about ongoing testing, such as a categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. dropdown not meeting accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) standards (#63531), and a problem with classic widgets.
Also, members were informed, that during testing (e.g., “Accordion 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.”), participants can report that no issues were found after comprehensive checks.
A proposed change in the meeting structure: start with discussions and open floor items, and save announcements for the end. This aims to capitalize on initial engagement and ensure action points aren’t overlooked.

8. Next Test Team Sessions

9 October 2025 at 3.00PM GMT: <patch-testing-scrub> in #core-test.
15 October 2025 at 2.00PM GMT: <patch-testing-scrub> in #core-test.
16 October 2025 at 3.00PM GMT: <patch-testing-scrub> in #core-test.
22 October 2025 at 2.00PM GMT: <test-chat> in #core-test

Props to @nikunj8866 and @mosescursor helping review these notes and offering feedback.

#core-test

Manuel Camargo 7:37 pm on October 7, 2025
Tags: core-test

Team Chat Agenda: 8 October 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 8 October 2025 at 2PM GMT, which is held in the #core-test Slack channel.

Agenda

Attendance
Note-taker and facilitator selection for the next meeting
- This session facilitator and note-taker is @sirlouen
- Next session facilitator and note-taker is @mosescursor
WordPress Ecosystem Announcements
- What’s new in Gutenberg 21.7? (24 September)
- Introducing again the New Test Team Reps 2025-2026
Test Team Announcements
- The Test Handbook Overhaul
- Remember to check Week in Test Post for weekly updated info
Call for Testing
Test Team Discussion
- Time to Launch the Handbook Overhaul: Assigning Tasks
- Proposal for creating an Archive Section in the Handbook
  - Archiving the FSE Outreach Experiment page
- Shall we maintain “Crawl your test site for errors” section?
Open Floor
- Got a topic? Add in comments below, or bring it up live during the chat.

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

Moses Cursor Ssebunya 7:23 am on October 6, 2025
Tags: core-test, gutenberg ( 73 )

Week in Test: October 6, 2025

Jump to: Calls for Testing | Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | 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:

Call for Testing: Accordion Block
Collaboration: add 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.-level comments:
- Actively developed for 6.9. See #66377
- Several existing issues have already been reported. See #71774
Call for Testing: Ability to Hide Blocks
Help test changes to template management

Call for Test Table Lead for WC Islamabad

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. Islamabad is happening on 18 – 19 October 2025, with 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/ on the 18th. They’re looking for an online table lead for Testing to guide their local community and they’re open to connecting over Zoom/Google Meet. If anyone from the team is interested, please comment on this post or reply on channel.

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 skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

Patch Testing 🩹

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:

PHPUnit Tests 🛟

The following tickets need PHPUnit tests built to accompany their respective patches:

#63878 – Backport: add support for text inputs on the elements API

6.9 Related issues need testing

The following 6.9 tickets need testing, those are having patches:

Profile Badge Awards 🎉

No Badges Issues this Week

Read/Watch/Listen 🔗

Gutenberg 21.8RC is now available.
Notes from the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committer meeting at WCUS 2025 are now available.
Bug Scrub Schedule for WordPress 6.9
WordPress 6.9 is planned for December 2, 2025, with BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 beginning October 21

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held for 2025.

2025 Schedule:

Wednesday, 08 October 2025 at 17:00 GMT+3 : <test-chat> in #core-test..
Thursday, 09 October 2025 at 18:00 GMT+3 : <patch-testing-scrub> in #core-test..

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

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

#core-test, #gutenberg

Krupa Nanda 6:23 am on October 6, 2025
Tags: core-test, full-site-editing ( 63 ), gutenberg ( 73 ), needs-testing ( 5 )

Call for Testing: Accordion Block

As part of the upcoming WordPress 6.9 release, we are introducing a brand-new 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., the Accordion block.

This block was first introduced in the Gutenberg 21.5 release as an experimental feature and is now being stabilised. More testing is needed to ensure its reliability and polish before it ships with the WordPress 6.9 release.

What is the Accordion block?

The Accordion block lets you display collapsible sections of content, which is ideal for FAQs, expandable information lists, etc.

The block acts as a container, i.e. Accordion that holds multiple child blocks, which we can consider as Accordion Items
By default, adding an Accordion block inserts two Accordion Items.
Each item contains a title and an expandable content area that can be toggled open or closed.

Note: In the latest specification, only one accordion item is inserted. This will the new behavior in 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/ 21.9 Release. Please check #72021 PR for more details.

Now, before we start testing, let’s understand the difference between the Accordion and the Details blocks.

While both blocks allow collapsible content, their structure and purpose differ:

Accordion block: Designed for multiple collapsible grouped sections, such as FAQ lists. It contains several Accordion Items inside a single parent block, as shown in the screenshot below.

Details block: Intended for a single collapsible section, for example, a single “Read more” toggle as shown in the screenshot below.

Test Steps

Please try out the Accordion block in the latest Gutenberg 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. (v21.5 or later). Here are some testing scenarios:

Visit Gutenberg > Experiments and check the option to “Enable experimental blocks”
Navigate to Post/Page or template
Verify you can add an Accordion block now.
Confirm that the Accordion Item is added with an Accordion Heading and an Accordion Panel (ref the screenshot above)
Edit item placeholders and add content inside the Accordion Panel
Save and confirm that expand/collapse both function as expected in the front end and the editor
Verify Reordering
1. Move Accordion Items up or down
2. Confirm that the order updates correctly in both the editor and the frontend
Styling & Settings: This only applies to all items when you work through the global styles. If you change the style of an item in a block instance, the style will not be reflected in other items.
1. Apply block-level style settings (colors, typography, background, etc).
2. Confirm that styles are reflected in all items consistently.
Verify the duplicate of the accordion block
Remove an existing item and ensure the block continues to function as expected

Discover more scenarios based on the different use cases and see if that works as expected. Refer to the visual below to understand how you can play around with different settings.

Testing Instruction

Why Your Testing Matters

Your feedback helps ensure the Accordion block offers a consistent, stable, and intuitive experience for all users, including the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) considerations. If you encounter any related issues, please report them here.

How to report an issue

Write down step-by-step instructions on how an issue can be reproduced. Also, attach a screenshot/screencap for better clarity.
Use the Test report plugin to collect all essential 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. information.
Before creating a new issue, check if there is a related issue has already been reported in the Guutenberg repo. If not, create a new one here.

Props to @wildworks, @muddassirnasim and @mosescursor for pre-publish review of this post.

#core-test, #full-site-editing, #gutenberg, #needs-testing

Krupa Nanda 7:41 am on October 4, 2025
Tags: core-test, full-site-editing ( 63 ), gutenberg ( 73 ), needs-testing ( 5 )

Call for Testing: Ability to Hide Blocks

A new feature is introduced in Gutenberg 21.8RC: the ability to hide blocks from the frontend.

This option provides more flexibility for working with content and layouts. Instead of deleting or moving 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. you don’t want published, you can temporarily hide it. The block remains in the editor, but it will not appear on the live site until the visibility is switched back on.

Why this matters

Makes it easier to experiment with different layouts without losing content.
Allows draft or placeholder content to stay visible in the editor but hidden from site visitors.
Encourages non-destructive editing and smoother collaboration.
Creates a foundation for future enhancements

Key Changes to Observe

In the editor,
- It adds a menu item to the block settings options to change the block’s visibility.
  - “Hide”: A “Hide” option appears on each block by default
  - “Show”: Clicking on “Hide”, the block setting toolbar should display the “Show” option.
- In the List view, the visibility of multiple blocks can be changed simultaneously.

Test Steps

Install and activate the Gutenberg plugin (V21.8RC). Alternatively, you can test this with this playground link.
Navigate to the post, page, or template.
Select the block and click on the “Hide” control from the toolbar settings
Observe that the block is no longer visible in the editor, and the “Show” control should be toggled on for that block (Observe the List view)
Check the change in the front end, and the block should be hidden
Now, turn off the hide setting in the editor
The block should reappear in the editor and the front end
Nested blocks: Place a few blocks inside a Group/Columns block and hide the parent.
1. Confirm that all inner blocks are hidden
Multiple instances: Hide different blocks across the page and verify that only the chosen ones are excluded from the frontend.

Testing Instruction

Since this feature is newly introduced, it needs testing, and feedback is especially valuable.

Please share:

Did the toggle behave as expected?
Did you run into inconsistencies between the editor and the frontend?
Were there any issues with nested, synced, or reusable blocks?

Your input will help refine this feature as it moves toward the WordPress 6.9 release.

Follow #71203 PR for more details. If you observe any related issues, please feel free to report them here.

📈Performance / Asset Check

Hidden blocks should not appear on the frontend, and their related CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site./JS should no longer be actively used. Optionally, you can verify this via the Network tab or CSS Coverage in DevTools. Visible blocks must continue loading normally. On small pages, coverage differences may be subtle; the key point is that hidden blocks do not add frontend markup or assets. Check #9213 PR for more details. If you would like to verify this, follow the steps in the comment.

If you’re unsure whether what you are experiencing is a bug, you can ask in the #outreach 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/.

Change Log

1.0.0 Initial Post

1.1.0 Add Performance check

Props to @wildworks @psykro for pre-publish review of this post.

#core-test, #full-site-editing, #gutenberg, #needs-testing

Krupa Nanda 6:49 am on September 29, 2025
Tags: core-test

Week in Test: September 29, 2025

Jump to: Calls for Testing | Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | 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:

Accordion Block: See PR: 64119
Collaboration: add 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.-level comments:
- Actively developed for 6.9. See #66377
- Several existing issues have already been reported. See #71774

Weekly Testing Roundup 🤠

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 skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

Reproduction Testing 🔁

Who? Any contributor.
Why? It is helpful to show an issue exists for other users in order to move a ticket forward for patching.

The following new tickets are awaiting review and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results: