Team Chat Agenda: 05th November 2025

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, 05 November 2025, 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

Team Chat Agenda: 22nd October 2025 

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, October 22, 2025, 5:00 pm GMT+3 , which is held in the #core-test Slack channel. Well wishers are all 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
Last Updated Wednesday, 22 October 2025 at 16:00 GMT+3

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

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

Test Chat Summary: October 8, 2025

On 8 October 2025 at 2PM GMT, <test-chat> started in #core-test facilitated by @sirlouen The agenda can be found here.

1. Attendance

@mosescursor @nikunj8866 @agulbra @dhavalkapadane @fakhriaz @muddassirnasim @passoniate (async) @dilip2615 (async)

2. Volunteer

This week’s note-taker was @sirlouen

3. WordPress Ecosystem Announcements

4. Test Team Announcements

5. Call for Testing

6. Test Team Discussion, Questions, and Blockers

1. Handbook Overhaul—Task Assignments

  • The meeting began with the launch of the Handbook Overhaul project, focusing on assigning tasks to contributors.
  • Each participant will be assigned at least one new page to create and two or three pages to review.
  • The objective is to ensure every single documentation page is properly replicated before the originals are deleted—anything not replicated will be lost.
  • Tasks for contributors fall into three categories:
    • Create: New pages to be created, primarily copied from the originals.
    • Review: Existing pages requiring review and verification.
    • Discuss: Pages to be discussed in any meeting, like the Archive section.
  • A second call-out will be made for more volunteers, who will then be assigned tickets.

2. Proposal: Archiving Old Sections

  • A proposal was presented to create an “Archive” section in the documentation for obsolete content.
  • The specific example raised was archiving the “FSE Outreach Experiment” page and similar sections not currently useful.

3. Section Review: “Crawl your test site for errors”

  • A specific section, “Crawl your test site for errors”, was discussed.
  • The group debated whether this section is still relevant to keep, with some members expressing doubts.
  • The decision was left open for further review and comments. Removal will be approached in the next meeting unless there are any arguments against it.

7. Closing and Open Floor

  • @fakhriaz commented about ongoing testing, such as a categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. dropdown not meeting accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) standards (#63531), and a problem with classic widgets.
  • Also, members were informed, that during testing (e.g., “Accordion 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.”), participants can report that no issues were found after comprehensive checks.
  • A proposed change in the meeting structure: start with discussions and open floor items, and save announcements for the end. This aims to capitalize on initial engagement and ensure action points aren’t overlooked.

8. Next Test Team Sessions

Props to @nikunj8866 and @mosescursor helping review these notes and offering feedback.

#core-test

Team Chat Agenda: 8 October 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 8 October 2025 at 2PM GMT, which is held in the #core-test Slack channel.

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 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

Team Chat Agenda: 24th September 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 24 September 2025 at 16:00 UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

  • Attendance
  • Note-taker and facilitator selection for the next meeting
    • This week’s facilitator is – @krupajnanda
    • This week’s note-taker is – Looking for a volunteer
  • 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.
    • Bug Scrub Schedule for WordPress 6.9
  • Test Team Announcements
  • Focal Group Updates
  • Questions/Blockers
  • Call for testers/visibility:
  • Open Floor
  • Got a topic? Add in comments below, or bring it up live during the chat.

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

Week in Test: September 23, 2025

Hello and welcome to another edition of Week in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Jump to: Calls for Testing | Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

Calls for Testing 📣

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following features need special attention:

  • Accordion Block: See PR: 64119
  • Collaboration: add blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-level comments:
    • Actively developed for 6.9. See #66377
    • Several existing issues have already been reported. See #71774

Weekly Testing Roundup 🤠

Weekly update: Test Team Update

Here’s a roundup of active tickets that are ready for testing contributions.

Did you know that contributions with the Test Team are also a fantastic way to level up your WordPress knowledge and skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

Reproduction Testing 🔁

Who? Any contributor.
Why? It is helpful to show an issue exists for other users in order to move a ticket forward for patching.

The following new tickets are awaiting review, and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results:

Patch Testing 🩹

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

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

PHPUnit Tests 🛟

Who? Any QA or PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php. developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. for quality and backward compatibility.

The following tickets need PHPUnit tests built to accompany their respective patches:

6.9 Related issues need testing

The following 6.9 tickets need testing those are having patches:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

  • To facilitate the development and testing of the Block 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.0 RC1 is now available for testing.
  • Bug Scrub Schedule for WordPress 6.9

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held for 2025.

2025 Schedule:

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

#core-test

Team Chat Agenda: 10th September 2025

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, 10 September 2025, 04: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

Team Chat Agenda: 28th August 2025 

Here is the agenda for the upcoming Test Team Chat scheduled for 28 August 2025 at 4PM 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 Summary: August 13, 2025

On 13 August 2025 at 4PM GMT, <test-chat> started in #core-test facilitated by @sirlouen The agenda can be found here.

1. Attendance

@oglekler @nikunj8866 @agulbra @callumbw95 and @getsyash

2. Volunteer

This week’s Note-taker was @sirlouen

3. Announcements

4. Test Team Updates

5. Focal Group Updates

6. Calls for Testers/Visibility

@agulbra, the main contributor to WordPress TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket #31992 on “Unicode email addresses”, has largely completed the development work but has been testing it himself, which is not ideal. @SirLouen emphasizes the need for independent testing and suggests that @agulbra prepare clear, detailed test cases so both technical and non-technical testers can contribute, aiming for at least three to four independent reports. Potentially during the next Patch Testing Triage next 18 August 2025 at 1.30PM GMT.

7. Test Team Discussion, Questions, and Blockers

Proposal to review the official Test Reports in Trac

The main topic is the proposal to review official Trac Test Reports related to the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. test team activities. @oglekler and @sirlouen discuss the existence and visibility of three main reports: Needs Testing, Needs Unit Tests and Needs Reproduction (with the last one being less accessible and considered inaccurate).

The proposal is to create specific queries for each report and holding a vote in one of the next official test team meeting to decide which queries should be accepted. The results would then be forwarded to the Core administration team for potential changes, as these reports directly affect the Test Team’s activities.

The overall idea is to formalize the process of selecting and refining these reports through the test team’s official meetings and votes. This process would help maintain effective tracking of testing tasks by having official and accurate reports that reflect the test team’s needs and priorities.

8. Open Floor

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

9. Next Test Team Sessions

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

#core-test