Tag Archives: gutenberg

Moses Cursor Ssebunya 11:37 am on December 1, 2025
Tags: , , , gutenberg,   

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 be 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: , , , gutenberg,   

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 be 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: , , gutenberg, ,   

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 be 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: , , gutenberg, , ,   

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 be 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: , , gutenberg,   

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 be 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: , , gutenberg, ,   

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 be 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/preface.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: , , , gutenberg, , ,   

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

Moses Cursor Ssebunya 7:14 am on October 24, 2025
Tags: , , , gutenberg, ,   

Test Chat Summary: October 22nd, 2025

On Thursday, October 22nd, 2025 at 05:00 PM GMT+3, <test-chat> started in #core-test facilitated by @mosescursor The agenda can be found here.

1. Attendance

In attendance was:
@sirlouen @nikunj8866 @rakib03029 @mobarak @r1k0 @rollybueno @fakhriaz @passoniate @shsajalchowdhury @harshalkadu @narenin

2. Volunteer

This week’s Note-taker was @mosescursor
Meet next week’s note taker @nikunj8866 

3. Test Team Discussions

  1. Time to Review the Test Handbook Overhaul:
    •  We are in the last lap for the test handbook completion!
      • @sirlouen reported that he had already contacted 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 to schedule a date to start syncing and also mentioned that the project is 99.99% complete, and once a date is confirmed, they will complete the final administrative tasks and proceed. @sirlouen also noted that @dd32 was copied in on the communication.
      • @sirlouen also shared that he is going to edit all current documentation pages to add 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 be the repository owner. https://github.com/ link and indicate that the pages are outdated. Once the sync is complete, those pages will be removed and replaced with new content. He also mentioned that work can begin on one or two GitHub pages now, starting with the badges page.
      • @nikunj8866 emphasized that the slugs needs to be observed as same before removing and archiving old pages
    • A few Tickets were pending Reviews and volunteers were assigned. We are almost there. All tickets were reviewed by meetings end and merge ready. @sirlouen will proceed to merge
  2. Proposal for creating an Archive Section in the Handbook.
    The archive section was supported in the last meeting and these two pages are among those to be first archived.
  3. We need to build a new page for 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
    @sirlouen is moving to Gutenberg tests and will do build the page

4. Open Floor

No additional topics were brought up during the open floor section of the meeting.

5. WordPress Ecosystem Announcements

Please receive the ECO system announcements

  1. Test Team Announcements
  2. Call for Testing
    Several Issues are available for testing ahead of the 6.9 release. Let’s help collaborate on these as well. Here is  a short list but more will surely be found especially after the 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. release last night

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 for helping review these notes and offering feedback.

#core, #core-test, #fse-outreach-program, #gutenberg, #make-wordpress-org-mobile, #make-wordpress-orgupdates

Moses Cursor Ssebunya 8:47 am on October 20, 2025
Tags: , gutenberg, , ,   

Week in Test: October 20, 2025

Week in Test: October 20, 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 📘

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 be 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. 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 that need reviews before merging and here are the pending Issues of the [MIRROR] Project 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/preface.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, #gutenberg, #make-wordpress-org-core, #make-wordpress-org-test, #make-wordpress-orgupdates

Moses Cursor Ssebunya 7:20 am on October 13, 2025
Tags: , gutenberg, ,   

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.

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:
    • 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://2017.us.wordcamp.org/contributor-day/ 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 be 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/preface.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 🔗

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, #gutenberg, #make-wordpress-org-test, #make-wordpress-orgupdates