Tag Archives: full-site-editing

Moses Cursor Ssebunya 11:37 am on December 1, 2025
Tags: , , full-site-editing, ,   

Week in Test: December 1, 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.

Table of Contents

Calls for Testing 📣

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

Test Handbook 📘

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

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

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

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

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

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

a. Patch Testing 🩹

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

The following tickets 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 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:

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

d. Handbook Review

Here are the current activities being discussed in the Test Handbook:

  1. We need to review https://github.com/WordPress/test-handbook/pull/98

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 (13) 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 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉
@fakhriaz
– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

2025 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 @sirlouen @oglekler for helping review this article and offering feedback

#core-test, #fse-outreach-program, #full-site-editing, #gutenberg, #make-wordpress-orgupdates

Moses Cursor Ssebunya 8:06 am on November 24, 2025
Tags: , , full-site-editing, ,   

Week in Test: November 24, 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.

Table of Contents

Calls for Testing 📣

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

Test Handbook 📘

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

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

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

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

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

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

a. Patch Testing 🩹

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

The following tickets 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 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:

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

  • Nothing for this week

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 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉
None this week. Please keep contributing.
– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

2025 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, #fse-outreach-program, #full-site-editing, #gutenberg, #make-wordpress-orgupdates

Moses Cursor Ssebunya 6:53 am on November 22, 2025
Tags: , full-site-editing, , ,   

Test Chat Summary: November 19th, 2025

On Wednesday, November 19th, 2025 at 04:00 PM GMT+2, <test-chat> started in#core-test facilitated by @sirlouen. The agenda can be found here.

1. Attendance

In attendance was:
@sirlouen @huzaifaalmesbah @rithika3 @r1k0 @oglekler @sajib1223 @noruzzaman @dhruvang21 @fakhriaz @mosescursor @harshalkadu @muddassirnasim

2. Volunteer

This week’s facilitator was @sirlouen
This week’s Note-taker was @mosescursor

3. Test Team Discussions

  1. Time to Review/Update the Test Team Reps Page.
    •  A recent discussion brought up 2 things
      • New contributors badge requirements
      • Test Reps eligibility for next year
    • We have identified that to join the Test Team, people should get some experience running these sessions. Something that is not hard as someone needs to know how to make a test Chat Agenda and Follow that for the meetings.
      • @sirlouen proposed that if a person ran a Test Chat Meeting, they would then be eligible for a Test Contributor Badge. This year, many people were nominated without any experience, and this is not acceptable
      • He also added that Test Scrubs is another activity that future Test Reps should do and hence Test Scrubs is also promoted for eligibility. For example: 2 test scrubs + 2 meetings will be enough for eligibility for Test Rep position with my proposal
        • Test scrubs can be initiated from today, but meetings will be initiated starting January 2026, and we will have a list when people sign up for it.
        • @oglekler added that a Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. must be experienced with all team activities before applying to become a Team Rep. This will save both the applicant and team any surprises.
          • @mosescursor suggested that Team Reps should come from the Test Team members. A position a person gets after cycling through the Test Team processes.
            • @oglekler said that Team reps and Team members will have to support the contributors to get to that level. This also calls for contributors interest.
      • A simple Q&A
        • How can a Person sign up for running a meeting?
          After January, during each meeting, the current Team Reps will be asking if anyone wants to run the meeting and we will also post the current “list” in case more than one user has proposed. When they ask, you can raise your hand and they will contact you, put you in the list, and explain all the steps on how to run the meeting. We are starting on January because we need the current reps to get a little more experience before starting to add new members to this
        • How can I run a Test Scrub?
          You can run one of these whenever you want. You can just contact @sirlouen or any of the current test reps, and we will make sure you learn the basics on how to run a good test scrub
    • @sirlouen will then be drafting the new page for reps.
    • Remember that now Forum discussions are happening in GitHub, and the discussions will be kept for a week before a decision is made.
      Feel free to write there whenever you want, send a new proposal, etc (remember that every proposal has to go first through a meeting like this and then 1 week to discuss 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/)
  2. 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 GitHub issues.
    • No progress in this regard.
      • Again, feel free to comment in any of these three, or if you are brave, send a PR with your proposal for any of the 3.
  3. For anyone that could be interested in becoming a Test Rep, or Test Team Member(like @sirlouen), who is not a Test Team Rep, but a Test team member), it’s important to engage in these kinds of things and promote things in general. It’s impossible to join the team from a passive position

4. WordPress Ecosystem Announcements

5. Open Floor

  • @sirlouen is working on developing a 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 protocol for the future. This is mainly driven by the many people struggling with testing in the previous scrubs. We have to understand that testing needs some technical skills, but many people have some skills but waste a lot of time trying to set up everything, and they never come back again after the setup.
    • @sirlouen is trying to lower the learning curve a little bit by introducing WordPress Playground Concepts. In these tests we will not be using wordpress-develop or wp-env anymore for testing, except for very complex tickets that need much more deep work.
      • These are going to first be tested in the 2 Testing Scrubs scheduled for Tomorrow.
        • Release Squad Testing scrub
        • and Regular testing scrub

6. Other Meetings

We usually have 2 meetings held every week and the times have been listed bellow for next week. an adjustment has been made to include the WordPress 6.9 Test Scrub and will soon be listed

Props to @nikunj8866, @sirlouen and @oglekler for helping review these notes and offering feedback.

#core-test, #full-site-editing, #gutenberg, #make-wordpress-orgupdates, #web

Moses Cursor Ssebunya 9:59 am on November 17, 2025
Tags: , full-site-editing, , , ,   

Week in Test: November 17, 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.

Table of Contents

Calls for Testing 📣

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

Test Handbook 📘

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

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

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

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

Here’s a roundup of active tickets that are ready for testing contributions. Did you know that contributions to the Test Team are also a fantastic way to level up your WordPress knowledge and 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. 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 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:

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

  • Nothing for this week

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 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉
None this week. Please keep contributing.
– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

2025 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 @sirlouen and @nikunj8866 for helping review this article and offering feedback

#core-test, #full-site-editing, #gutenberg, #make-wordpress-org-mobile, #make-wordpress-orgupdates, #web

Moses Cursor Ssebunya 8:27 am on November 10, 2025
Tags: , full-site-editing, ,   

Week in Test: November 10, 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.

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:

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

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.
  • We are currently under review of the home page and the PR is here for review.
  • We also need a new draft for the Team Reps for discussion in the next Test chat.

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

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 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉
@dhruval04

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

2025 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 @sirlouen @nikunj8866 for helping review this article and offering feedback

#core-test, #full-site-editing, #gutenberg, #make-wordpress-orgupdates

Moses Cursor Ssebunya 8:26 am on October 31, 2025
Tags: , full-site-editing, , ,   

Week in Test: November 3, 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:

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

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 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉
@passoniate @jdahir0789 @gulamdastgir04

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

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

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

#core-test, #full-site-editing, #gutenberg, #make-wordpress-org-mobile, #make-wordpress-orgupdates

Moses Cursor Ssebunya 6:43 am on October 27, 2025
Tags: , , full-site-editing, , , ,   

Week in Test: October 27, 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.

Jump to: Calls for Testing |Test Handbook | Weekly Testing Roundup | WordPress Core Testing | Gutenberg Testing | 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:

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

Test Handbook 📘

We are in the Final Review of 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 few weeks, a good amount of test contributors have embarked on the journey of reviewing our new Test Handbook based on Github. Reviews are underway and the final process set to start. The handbook is awaiting one meeting and will be fully replaced with the new GitHub based content.

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:

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.
Badge awarding has been paused until the Test Handbook migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. is complete. Keep contributing and we will get to you

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

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

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

#core-test, #fse-outreach-program, #full-site-editing, #gutenberg, #make-wordpress-org-mobile, #make-wordpress-orgupdates, #web

Krupa Nanda 6:23 am on October 6, 2025
Tags: , full-site-editing, ,   

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:

  1. Visit Gutenberg > Experiments and check the option to “Enable experimental blocks”
  2. Navigate to Post/Page or template
  3. Verify you can add an Accordion block now.
  4. Confirm that the Accordion Item is added with an Accordion Heading and an Accordion Panel (ref the screenshot above)
  5. Edit item placeholders and add content inside the Accordion Panel
  6. Save and confirm that expand/collapse both function as expected in the front end and the editor
  7. Verify Reordering
    1. Move Accordion Items up or down
    2. Confirm that the order updates correctly in both the editor and the frontend
  8. 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.
  9. Verify the duplicate of the accordion block
  10. 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

  1. Write down step-by-step instructions on how an issue can be reproduced. Also, attach a screenshot/screencap for better clarity.
  2. 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.
  3. 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: , full-site-editing, ,   

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

  1. Install and activate the Gutenberg plugin (V21.8RC). Alternatively, you can test this with this playground link.
  2. Navigate to the post, page, or template.
  3. Select the block and click on the “Hide” control from the toolbar settings
  4. 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)
  5. Check the change in the front end, and the block should be hidden 
  6. Now, turn off the hide setting in the editor
  7. The block should reappear in the editor and the front end
  8. Nested blocks: Place a few blocks inside a Group/Columns block and hide the parent.
    1. Confirm that all inner blocks are hidden
  9. 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

Jonathan Bossenger 8:31 am on October 3, 2025
Tags: full-site-editing, ,   

Help test changes to template management

Update: this feature has been punted to WordPress 7.0

A recent update to the Site Editor template management system has significantly enhanced WordPress template management by providing greater flexibility and control over the template editing experience. It is now possible to view created templates separately from theme templates, store more than one template per template type (or slug), edit templates and save them without making them active, manage template revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. more effectively, and mark specific templates as active or inactive according to requirements.

For more context on the history behind this change, read through the following proposal on GitHub

Key Changes

  • Template Management: Allows multiple templates with the same target slug and introduces the ability to switch between them by setting one as “active.”
  • Theme templates remain the “source of truth”: To edit a theme template, one first needs to create a duplicate of it as a Created Template and edit that template.
  • Theme Template Control: Users can now disable theme templates (except the essential index template)
  • New 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.: Adds “Active templates” and “Created Templates” views in the Site Editor
  • APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. Simplification: User templates now use standard Post Type REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/ endpoints
  • Enhanced Features: Enables revisions, duplication, and trashing through normal Post actions

Benefits

  • Created templates are retained when switching themes
  • Users can disable template edits when needed
  • New templates can be created without immediately publishing
  • Templates can be added for all slugs, not just missing ones
  • Improvements to template revisions, template duplication, and deleting templates
  • And more. For full details, see the PR description

Testing Instructions

  1. Install and activate the Gutenberg Nightly plugin from 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/ Times, or use this Playground link
  2. Navigate to Site Editor > Templates and test the new template management features
  3. Verify that you can see template categories for Active, Custom, and theme templates.
  4. Test custom theme templates
    1. Create, edit, and save a custom theme template, and confirm it only appears in the Created templates list.
  5. Test active templates
    1. Create multiple templates for the same target slug (ie, single-post) and ensure you can activate/deactivate different templates, and that the front-end rendering uses the correct template.
    2. Confirm that when activating one template, the other templates for that slug are marked as inactive.
    3. Test that you can activate a template in the template editing view.
  6. Test default template fallback
    1. Deactivate a theme template and ensure the correct fallback template (in line with the template hierarchy) is used instead.
  7. Test switching themes
    1. Once you’ve created a custom template, switch to a different 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. theme and ensure the custom template remains.
  8. Test that template revisions, duplicating templates, and deleting templates work as expected.

Testing Steps

Breaking Changes

  • Changes to getEditedPostId and getCurrentPostId may impact plugins
  • Plugins should migrate to use getEditedPostSlug instead

Logging bugs and discussions

All existing bugs are being tracked in the following tracking issue in the Gutenberg 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/ repository: https://github.com/WordPress/gutenberg/issues/71735

If you encounter any new bugs related to this feature during testing, please log them as new issues and mention them in the above tracking issue.

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

+make.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//coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., +make.wordpress.org/themes

Props to @krupajnanda, @annezazu, @bph, and @juanmaguitar for assistance in reviewing this post.

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