Tag Archives: core-test

Ozgur Sar 1:01 pm on January 31, 2026
Tags: core-test,   

Test Chat Summary: 29th January 2026

On January 29, 2026 15:00 GMT, <test-chat> started in #core-test facilitated by @ozgursar. The agenda can be found here.

1. Attendance

In attendance was:
@nikunj8866 @fakhriaz @sirlouen @ozgursar @wing.louie @huzaifaalmesbah @juanmaguitar @r1k0 @mosescursor @mebo (async) @mohkatz (async)

2. Volunteer

This week’s facilitator was @ozgursar

This week’s Note-taker was @ozgursar

3. Test Team Discussions

Proposal to archive old test reports

@sirlouen presented a proposal to archive old test reports that do not belong to the test team or are obsolete with the new structure. The goal is to move toward newer versions of the test reports structure.

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

A proposed new version of the test reports pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. is being tested and is available at:

The team can test using WordPress Playground or download and install as a plugin to a local WordPress develop environment. @sirlouen aims to finalize the version before February and will send a PR once feedback is received. @nikunj8866 will also review and share feedback.

Officialize the two test reports

This was a major agenda item focused on making official decisions about test reports structure. Currently there are two official reports:

  1. Needs Reproduction (https://core.trac.wordpress.org/report/69)
    • Issues: Doesn’t have a good slug, filters the report weirdly (includes reporter-feedback, only accounts for bugs), not on homepage
  2. Patches Needing Testing (https://core.trac.wordpress.org/tickets/needs-testing)
    • Status: Has correct slug and is on homepage

Proposal discussed: Two alternatives were presented:

Option 1: Make needs-reproduction report official

  • Add it to homepage with a correct slug (/needs-reproduction)
  • Fix the filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. parameters

Option 2: Unify into a single report that will include both Patch Testing and Needs Reproduction

Rationale for unification: Since anyone can add the needs-testing keyword to tickets, without solid principles on how to identify if a test needs reproduction or patch testing, confusion is inevitable. Testers need to do full analysis work regardless of keywords assigned to tickets, as the keywords cannot be reliably trusted.

Vote results: 5 to 1 in favor of having a single unified report

Next steps: Team members can comment on the handbook ticket until Monday. @sirlouen will send the final decision to 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..

4. Open Floor

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. Asia 2026 Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/

@nikunj8866 shared that @Krupa from the Contributor Day team reached out regarding Test Team Table Leads for WordCamp Asia 2026 Contributor Day.

Anyone attending WordCamp Asia 2026 in person and interested in leading the Test Team table should reply in the thread or reach out to @nikunj8866 directly. The handbook provides guidance on the role and responsibilities.

5. Announcements

6. Other Meetings

Props to @sirlouen, @mosescursor, @nikunj8866 for reviewing the post.

#core-test, #test-chat-summary

JuanMa Garrido 3:33 pm on January 29, 2026
Tags: core-test,   

Test Chat Summary: 22nd January 2026

On Wednesday, 22 January 2026, 03:01 PM UTC, <test-chat> started in #core-test facilitated by @juanmaguitar. The agenda can be found here.

1. Attendance

In attendance was:
@juanmaguitar @nikunj8866 @sirlouen @mosescursor @ozgursar @pavanpatil1 @sajib1223 @r1k0 @mohkatz @fakhriaz @alexcu21 @huzaifaalmesbah

2. Volunteer

This week’s facilitator was @juanmaguitar

This week’s Note-taker was @juanmaguitar

3. Test Team Discussions

“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. testers” for the new Test Contributor Pathway course

@sirlouen announced that the Test Contributor Pathway course will be launching on the Learn site in the coming weeks. The team is looking for beta testers to review the videos and provide feedback. Community members interested should contact @sirlouen directly for private access.

Creating a new page in the handbook with a “template” for Test Chats

The team discussed creating documentation for facilitating test chat meetings. @sirlouen explained the goal is to document templates and guidance so anyone can run a test chat. @juanmaguitar noted he’s currently following steps from a previous meeting.

Contributors can submit pull requests to the test-handbook GitHub repository, or open issues with ideas if a full PR feels too daunting.

Add labels to posts that are regularly posted on make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//test

@juanmaguitar proposed adding consistent tags (week-in-test, test-chat-summary, test-chat-agenda) to recurring posts to improve discoverability, similar to Gutenberg posts. See full suggestion in Slack.

The discussion focused on tags vs categories. The main advantage of tags is they persist when duplicating posts or using templates, while categories can be forgotten. However, categories are prominently displayed in the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. @mosescursor noted the “Kibble” default categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. is misconfigured.

@juanmaguitar will open 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 by the repository owner. https://github.com/ issue (#109) to continue the discussion. The topic requires more thinking and will be revisited once there’s more consensus.

Call for help, building 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/ bot for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

@sirlouen requested help building a Slack bot for Core testing announcements, similar to the existing Gutenberg announcer. The goal is to automatically notify #core-test whenever a needs-testing tag is added to a Core ticket.

PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php scripts that interact with TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. already exist at meta.trac.wordpress.org. More details are available in Trac ticket #8157. @juanmaguitar expressed interest in helping with this.

4. Open Floor

No items were raised during the open floor.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

Props to @sirlouen for reviewing this post

#core-test

#test-chat-summary

Ozgur Sar 11:29 am on January 28, 2026
Tags: core-test,   

Test Team Chat Agenda: 29th January, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday 29 January 2026 at 15:00 GMT, 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, #test-chat-agenda

Moses Cursor Ssebunya 6:39 am on January 28, 2026
Tags: core-test, , , ,   

Week in Test: January 27, 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 by the repository owner. https://github.com/

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

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

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

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

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

a. Patch Testing 🩹

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

The following tickets (2) 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 (169) 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 (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 (2) 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 🎉

  • none awarded this week

– 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

JuanMa Garrido 11:00 am on January 21, 2026
Tags: core-test,   

Team Chat Agenda: 22nd January, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 22 January 2026, 03: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.

#test-chat-agenda

#core-test

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

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 by the repository owner. https://github.com/

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

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

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

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

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

a. Patch Testing 🩹

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

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

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 by 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: core-test   

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: core-test, , , ,   

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 by the repository owner. https://github.com/

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

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

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

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

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

a. Patch Testing 🩹

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

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

Manuel Camargo 12:51 pm on January 6, 2026
Tags: , core-test,   

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