Category Archives: Summary

Manuel Camargo 1:39 pm on February 6, 2026
Tags:   

Test Chat Summary: 5th February 2026

1. Attendance

In attendance was:
@fakhriaz @huzaifaalmesbah @ozgursar @supernovia @mosescursor @sajib1223 @andrewssanya @mohkatz @zuveria @r1k0 @sirlouen

2. Volunteer

3. Test Team Discussions

Switching to Monthly Newsletter

The team discussed changes to the monthly newsletter format. The decision was made to remove the “tests to be done” section and replace it with a new “call for testing” section that aggregates requests from other groups. Additionally, the newsletter will include announcements, news, and ideas from team members. @mosescursor will comment on the related 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 with further details.

New Triage Guide

@sirlouen presented the diagram proposed by @juanmaguitar in the “Add TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Keyword Triage Guide for Test Team Members” initiative. During the discussion:

  • @ozgursar raised concerns about whether bug reproduction should be included, noting it could be confusing.
  • @r1k0 commented that the guidance on what to write for expected results is not clear enough.

@sirlouen requested that team members add more comments to the GitHub issue to help refine the new guide.

Announcements for Test Team Promotions

Promotions were announced for the following team members: @ozgursar, @r1k0, @juanmaguitar, and @huzaifaalmesbah.

4. Open Floor

  • @sirlouen expressed hope that the team can move toward an automated testing protocol in the future. Several ideas were discussed around improving the onboarding experience for new contributors:
  • @shazzad suggested adding a special keyword to identify easy tickets for new test team members.
    • @fakhriaz agreed with the idea.
    • @supernovia suggested the name good-first-test for this keyword.
    • @sirlouen had some concerns looking at the triage workflow: when a new test ticket appears in chat, a team member should triage and review it, removing the needs-testing keyword if the ticket cannot be tested, but leaving it if it can be tested. Placing the good-first-test keyword on tickets doesn’t seem to find a good place in this workflow. Further refinement is required to confirm that this keyword will truly fit.
    • @shazzad will open a ticket in the GitHub test-handbook repository to formalize this idea.
  • The team also discussed the need for weekly test team updates on current Needs Reproduction and Needs Patch Testing tickets. @mosescursor will handle this responsibility until @nikunj returns.
  • @mosescursor asked if @r1k0 would be joining the contribution day in Uganda on March 14. @r1k0 will check his schedule and confirm.
  • @sirlouen reminded the team that any AI tools used during testing should be noted in the footnotes of test reports.
  • @mosescursor will request huddle permission from 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 facilitate future voice chats.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

Props to @supernovia, @huzaifaalmesbah, @ozgursar, and @r1k0 for helping review this article and offering feedback.

#test-chat-summary

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

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

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

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

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 6:53 am on November 22, 2025
Tags: , , , ,   

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

Nikunj Hatkar 3:18 am on November 11, 2025
Tags:   

Test Chat Summary: November 05th, 2025

On Wednesday, 05 November 2025, 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 @sirlouen @mosescursor @r1k0 @rakib03029 @abduremon(async) @fakhriaz (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

  1. The Test Handbook is now synced with GitHub.
    • Thanks to all contributors, especially @sirlouen, for leading the effort. Minor issues may remain, so everyone is encouraged to review and submit fixes.
  2. Time to Review/Update the Test Team Handbook Index Page.
    • The team discussed reviewing and updating the Test Handbook Index Page to remove outdated content and align it with current team activities.
    • @sirlouen suggested drafting one or more revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. for discussion before finalizing the changes.
    • Full Site Editing (FSE) Outreach and several other outdated testing types (e.g., unit testing, usability testing, triage/bug scrubbing) will be removed.
    • The new focus areas for the Test Team will include Patch Testing Scrubs, Issue Reproduction Testing, and End-to-End (E2E) Testing.
    • Proposed changes were submitted in Updating the Test Handbook Homepage #89 for review and feedback.
    • The Test Handbook will get new pages for Feature & Enhancement Testing (#90), E2E Testing (#91), and Patch Testing Scrubs (#92); contributors can update these 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.

4. Open Floor

  • @sirlouen brought up Issue #9 regarding documenting current team goals and initiatives, and discussed adding a brief note about this in the Handbook homepage. Contributors can follow and participate in the discussion through the issue.

5. Announcements

Please receive the ECO system announcements

  1. Test Team Announcements
  2. WordPress Ecosystem Annoucement
  3. Call for Testing
    Several issues are available for testing ahead of the 6.9 release. Please help collaborate on these! Here’s a short list, but more will surely be discovered.

6. Next Test Team Sessions

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.

Props to @sirlouen and @mosescursor for helping review chat summary.

#core-test

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

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

Krupa Nanda 6:26 am on September 29, 2025
Tags:   

Test Chat Summary: September 24, 2025

On Wednesday, September 24, 2025 at 12:00 AM GMT+8, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance

@krupajnanda @oglekler @sirlouen @nikunj8866(asnyc) @shsajalchowdhury @dilip2615 @callumbw95 @sajjad67 @fakhriaz @muddassirnasim(async) @passoniate

2. Volunteer

This week’s Note-taker was @krupajnanda

3. Announcements

  • To facilitate the development and testing of the 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. Commenting feature, @wildworks has created a plugin to bulk insert multiple block comments. Please feel free to use it if you need it.
  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 21.7 is expected to be released today. Keep an eye here for the latest update.
  • Bug Scrub Schedule for WordPress 6.9

4. Test Team Updates

5. Calls for Testers/Visibility

6. Focal Group Updates

@sirlouen has started building a dedicated Testing 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 to replace the current one with plan to introduce new features along with a plan to redesign the Handbook sections for reports, which will be used for the new testing plugin for clarity. For more details please revisit meeting history here.

Badge Requirements

@sirlouen suggested increasing the minimum number of test reports from 1 to 5 tickets and proposed removing the requirements related to unit/e2e tests and contributing to WordPress test suites, as those are not directly related to the part of Test Team 

8. Questions

@fakhriaz asked for recommendations on books, YouTube channels, and the best path to become an expert in testing and coding. @sirlouen suggested reading “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.: The Right Way” for PHP, and checking the 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/ documentation and resources to learn about WordPress testing.

@krupajnanda mentioned everyone that the WordPress 6.9 release is coming soon, with 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. 1 expected in a month. They encouraged everyone to explore the new features, fixes, and enhancements, and to keep an eye on the roadmap and the “Week in Test” post for early testing opportunities.

8. Next Meetings

#core-test

Nikunj Hatkar 3:34 pm on September 12, 2025
Tags:   

Test Chat Summary: September 10th, 2025

On Wednesday, 10 September 2025, 04:00 PM UTC, <test-chat> started in  #core-test facilitated by @nikunj8866. The agenda can be found here.

1. Attendance

@nikunj8866 @oglekler @krupajnanda @dilip2615 @pmbaldha @doreen233 @sirlouen

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Announcements

4. Test Team Updates

5. Focal Group Updates

@sirlouen mentioned that Contributors Onboarding & Coffee Hours session will be replaced with Patch Testing Scrubs, held after the weekly #core Live Bug Scrubs (Thursdays @ 1PM GMT).

6. Calls for Testers

Here are some tickets that need testing. This is a call for community testers to take them up whenever possible.

7. Test Team Discussion, Questions, and Blockers

7.1 Tested Keyword Proposal

  • @oglekler suggested introducing tested a keyword in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. so contributors can explicitly sign off with their name after testing a patch. This would add accountability and clarity to the testing process.

7.2 Current State of Testing

  • @sirlouen noted that testing is still happening somewhat at random, though it has improved compared to last year. He also pointed out there is no consistent or official testing protocol in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • @oglekler agreed, saying that currently contributors just “rummage around” to find something to test.

7.3 Quality Assurance vs. Testing

  • @oglekler highlighted that the conversation should focus on Quality Assurance, not just testing. In commercial development, releases do not go live without QA approval, and this should become a WordPress standard.

7.4 Double-Test Enforcement

  • @sirlouen proposed enforcing a minimum of two independent tests before committing a patch, similar to the double sign-off required for RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. backports. He also admitted this may not be feasible right now due to limited testing resources.

7.5 Test Scrubs & Releases

  • @sirlouen suggested Test Scrubs could run side-by-side with bug scrubs during releases.
  • @krupajnanda explained that during release cycles, triage is often converted into a test scrub by targeting tickets scheduled for the upcoming version.
  • @sirlouen stressed that enforcing a “two-test” policy would make tickets nearly ready to commit once they are milestoned.

@sirlouen proposed the following actions:

  • Update the weekly report to include solicited tests.
  • Maintain a clear queue of requested tests (via Trac reports or another tool).
  • Keep the queue short with support from ongoing scrubs.

8. Open Floor

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

9. Next Test Team Sessions

Props to @krupajnanda and @sirlouen for helping review these notes and offering feedback.

#core-test