Tag Archives: web

Moses Cursor Ssebunya 1:55 pm on December 22, 2025
Tags: , , , , , web   

Test Chat Summary: December 17th, 2025

On Wednesday, December 17th, 2025 at 04:00 PM GMT+2, started in#core-test facilitated by @mosescursor. The agenda can be found here.

1. Attendance

In attendance was:
@fakhriaz @nikunj8866 @huzaifaalmesbah  @noruzzaman  @sirlouen @oglekler @r1k0 @abduremon @Dhruvang21 @gautammkgarg @mebo

2. Volunteer

Meeting started by explaining Note takers and Facilitators so people can take up the roles.

  1. Note takers are simply people who summarize the happening of the Test Chat and they always publish a test Chat summary like this one here.
  2. Facilitators are simply people that chair or facilitate a test team chat.
    These follow the agenda that is proposed and ensure that every one gets a voice.
    A sample Meeting is like the one held here.

These 2 can be done by the same person in the same instant however we encourage multiple people to do it to increase on the proof reading and collaboration

3. Test Team Discussions

  1. Time to Review/Update the Get Set Up for Testing Page.
  2. Time to Comment Back/Update the Test Team Reps Page.
  3. 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 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/ issues.
    • @sirlouen got to a conclusion that currently we don’t have enough resources to have the wheel moving
      • all the areas mentioned above require a good thought and a suggestion to expand the team was brought up.
  4. Test Team Training Program & Restructuring Plans for 2026
    • @sirlouen is leading the program.
    • Previously, mentorship was insufficient so now a full training was advised. A program in the test team that will bring in Champions
      • A call for as many people as possible was made. People that will be committed to the program and see it through
    • @nikunj8866 sighted it as a great learning opportunity for anyone who wants to become a future Test Team representative.
      • @sirlouen added that it won’t only make team reps but also Power Members.
    • @sirlouen will pause current Handbook activity in preparation for the program in the next 2 weeks. Announcement made here highlighting the requirements to join and all the information about the program.

4. Open Floor

5. WordPress Ecosystem Announcements

6. Other Meetings

We usually have 2 meetings held every week. This is the last test-chat meeting for this year and Tomorrow’s patch testing session will be the last for this year.

  • Happy Festivities, See you again Next Year.
  • Happy new Year 2026

#core-test, #fse-outreach-program, #full-site-editing, #gutenberg, #make-wordpress-orgupdates, #web
Moses Cursor Ssebunya 1:06 pm on December 17, 2025
Tags: , , , , web   

Team Chat Agenda: 17th December, 2025

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, 3rd December 2025 at 16:00 GMT+2, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

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

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

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

Moses Cursor Ssebunya 1:43 pm on December 15, 2025
Tags: , , , , web   

Week in Test: December 15, 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 (4) 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 (205) 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:

c. 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
  • Test Team Discussions
    • Time to Review/Update the Get Set Up for Testing Page.
    • Time to Comment Back/Update the Test Team Reps Page.
    • 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.

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 (1) have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

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:

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉

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

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

Moses Cursor Ssebunya 6:53 am on November 22, 2025
Tags: , , , , web   

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

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 6:43 am on October 27, 2025
Tags: , , , , , , web   

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

Ryan Boren 7:11 pm on July 28, 2015
Tags: , , , , , , , , , web   

Media, Editor: Image captions containing <— are truncated, Macnchrome

With 4.3-beta4-33463.

#4-3, #beta, #captions, #chrome, #editor, #macos, #media, #needs-ticket, #visual-bug-report, #web

Ryan Boren 7:19 pm on July 14, 2015
Tags: , , , , , , , web   

Customize: Change site icon via customize, iPhone 6+

With 4.3-beta2-33249.

Notes:

  • I couldn’t get cropping to work.

#16434, #4-3, #beta, #customize, #ios, #phablet, #site-icons, #web