Pooja Derashri 12:04 pm on March 12, 2024  

Highlighted Posts

Categorize a post as Highlight to add it to this section.

Moses Cursor Ssebunya 6:26 am on January 20, 2026
Tags: , , , , ,   

Week in Test: January 19, 2026

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 (0) have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

  • No tickets this week

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 (191) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, then provide a bug reproduction report:

c. Test Team Issues

Here are the current activities being discussed in the Test Team Github:

  1. We need to review the Test Team Issues. If you have a possible solution, comment in the Issue or submit a PR.

2. GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ Testing

👋 Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets (0) 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.

  • Nothing this week

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:

  • None this week

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
  3. Call for Testing

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings. The schedule is being worked on and final schedule will be shared after finalizing the discussion

Current 2026 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

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

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

Nikunj Hatkar 11:37 am on January 19, 2026
Tags:   

Test Chat Summary: January 14th, 2026

On Wednesday, 14 January 2026, 02:00 PM UTC, <test-chat> started in  #core-test facilitated by @nikunj8866. The agenda can be found here.

1. Attendance

In attendance was:
@nikunj8866 @fakhriaz @huzaifaalmesbah @sirlouen @shanemuir @harshalkadu @pavanpatil1 @r1k0 @369work @saqib @juanmaguitar @ozgursar @hage (async) @mebo (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

  1. Time to Comment Back/Update the Get Set Up for Testing Page.
  2. Time to Review/Update the Test Core Tickets with Playground Page.
  3. @sirlouen shared 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/ issue #99 proposing a redesign of the Test Team Updates report.
    • The new format aims to be simpler, focusing on 4 reports across 2 sections (CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and Editor).
    • Only two key data points will be included: Current totals per categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. and 2-week changes per category (Closed tickets were considered low value and can be removed.)
    • @nikunj8866 noted the discussion, will review the GitHub thread in detail, and prepare a draft for the next report for team review before publishing.
  4. @sirlouen mentioned that the new Test Reports should be officialized after the training program ends, around February.
    • GitHub issue #100 – Officialize the Test Reports was shared as a follow-up.
    • No further action required at this time; the topic will be revisited after the training period.
  5. @juanmaguitar introduced an experimental Playground-based tool to simplify the WordPress testing setup(https://github.com/Automattic/experimental-wp-dev-env).

4. Open Floor

  • @sirlouen proposed moving the Test Team meetings from bi-weekly to weekly during the training program to increase participation and help trainees get involved in running meetings.
  • It was suggested to change the meeting day and time to better align with training sessions, moving away from Wednesdays.
  • A new proposed meeting structure was shared:
    Weekly Patch Testing Scrub: Tuesday @ 3:00 PM GMT
    Weekly Test Team Chat: Thursday @ 3:00 PM GMT
    Monthly Recorded Voice Session: First Thursday of each month @ 3:00 PM GMT
  • The monthly voice session will be recorded (via Huddle or Zoom) to allow asynchronous participation.
  • Patch testing sessions will also run weekly, with @nikunj8866 facilitating the next session, followed by training program members for the coming weeks.
  • The proposal has been documented in GitHub issue #103 for feedback and discussion before finalizing.
  • Once finalized, the Meetings calendar will be updated accordingly.
  • @huzaifaalmesbah asked about supporting TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. diff/patch files in WordPress Playground to make testing easier for contributors.
    • @sirlouen shared that this idea had been discussed earlier with the Playground team, but it does not seem easy to implement.
    • A GitHub PR-based workflow was suggested as a more modern and preferred approach.
    • @sirlouen followed up by raising the question in the #playground 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/. channel to explore possible alternatives, such as using a diff URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org.
  • @ozgursar asked whether there is any priority (such as milestones) when querying tickets in Trac.
    • @sirlouen explained that once the reports are officially active, milestoned tickets would naturally take priority.
    • Since the reports are not official yet, contributors are free to pick tickets in any order for now.

5. Announcements

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
  3. Call for Testing

6. Other Meetings

#core-test

Nikunj Hatkar 11:17 am on January 14, 2026
Tags:   

Team Chat Agenda: 14th January, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, 14 January 2026, 02:00 PM UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

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

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

#core-test

Moses Cursor Ssebunya 10:29 am on January 12, 2026
Tags: , , , ,   

Week in Test: January 12, 2026

Happy New Year 2026! To more wins and celebrations in our team and more

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 (5) 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 (202) 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. Test Team Issues

Here are the current activities being discussed in the Test Team Github:

  1. We need to review the Test Team Issues. If you have a possible solution, comment in the Issue or submit a PR.

2. GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ Testing

👋 Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets (0) 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.

  • Nothing this week

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:

  • None this week

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉

  • None this week

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

🚨 There will not be any more  #core-test meetings held in 2025.

2026 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

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

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

Nikunj Hatkar 4:46 am on January 9, 2026
Tags: ,   

X-post: Test Team Update: 5 January, 2026

X-post from +make.wordpress.org/updates: Test Team Update: 5 January, 2026

Nikunj Hatkar 4:23 am on January 9, 2026
Tags: ,   

X-post: WordPress 7.0 Call for Volunteers

X-comment from +make.wordpress.org/core: Comment on WordPress 7.0 Call for Volunteers

SirLouen 12:51 pm on January 6, 2026
Tags: , ,   

Launch Information for the Test Team Training Program

Finally, we are ready to launch the first Test Team Training Program! Here are the key details and steps for the launch.

Launch Date

The official launch date for the Test Team Training Program is January 8, 2026. The program will last for a duration of 4 weeks.

Participants have been already informed about the program’s detailed expectations.

About the time schedule, sessions will be held twice a week on Tuesdays and Thursdays at 16:00 UTC, starting on Thursday, January 8th, 2026 at 04:00 PM GMT

Program Overview

All the information can be reviewed in the Test Team Training Program announcement.

The program is designed to provide comprehensive training for new and existing members of the Test Team. It will cover various aspects of testing, including testing practices, test team processes, and a lot of feedback and introspection to improve collaboration pathways.

The training sessions are not strictly structured. They will include a mix of presentations, hands-on activities, group discussions, and Q&A sessions to ensure an engaging learning experience. This training is meant to be interactive and to shape the future of the Test Team.

There will be no recorded sessions to encourage live participation and interaction, and one of the main intentions will be to materialize the participants experiences into a comprehensive guide for future members of the Test Team.

Introductory Material

To prepare for the training sessions, participants are encouraged to review the following introductory materials:

  1. If you don’t have good experience with local testing environments, please check the Local Testing Environment Setup Guide (Part 1)(Part 2).
  2. Familiarize yourself with the WordPress Test Team Handbook and the GitHub repository for the Test Team.
  3. Review the Playground for Plugin Developers guide to get a few tips on how to build basic blueprints for testing with plugins and Playground.

Despite none of these materials being mandatory to get started, they will help participants to get the most out of the training program.

Selected Participants

After a deliberate selection process, we have finalized the list of participants for the Test Team Training Program.

Given that more than 20 members expressed interest, we have increased the number of participants to 9 to accommodate more interested members.

The criteria for selection included:

  • Having already some active involvement in the Test Team was preferred.
  • Enough available time to commit to the full duration of the program.
  • Technical skills were not a major deciding factor but have played a role in the selection.
  • Contribution history to the WordPress project and community was also considered.

The following individuals have been selected to participate in the Test Team Training Program:

  1. Ozgur Sar (@ozgursar)
  2. Erick Wambua (@r1k0)
  3. William Patton (@williampatton)
  4. Umera Ghori (@umeraghori)
  5. Huzaifa Al Mesbah (@huzaifaalmesbah)
  6. Shazzad Hossain Khan (@sajib1223)
  7. Mohammed Kateregga (@mohkatz)
  8. Saqib Ali (@saqib59)
  9. Juan Manuel Garrido (@juanmaguitar)

🎉 We congratulate all the selected participants and look forward to their active involvement in the program.

Props to @mosescursor for helping review this article and offering feedback.

#contributing-wordpress, #core-test, #test-contributors

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

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

  • We have introduced a bot that informs of new gutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ issues coming for testing. This posts directly in the 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/. channel
    • @sirlouen recommended adding an emoji like this :white_check_mark:  if you are going to be doing the testing report.
    • This helps for quick assignment of tasks and getting them cleared quickly.
    • Here people get a chance to know the tests required and even do them without having to wait for a Patch-testing session.
      • Infact this could also end the patch testing sessions when the new training is implemented
        • With this new notifier, anyone could jump in

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:01 pm on December 22, 2025
Tags: , , , , , , test team reps   

Week in Test: December 22, 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 (204) 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 (0) 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.

  • Nothing this week

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:

  • None this week

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉

  • None this week

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

🚨 There will not be any more  #core-test meetings held in 2025.

2026 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

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

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

Nikunj Hatkar 12:14 pm on December 22, 2025
Tags: ,   

X-post: Test Team Update: 22 December, 2025

X-post from +make.wordpress.org/updates: Test Team Update: 22 December, 2025