Yearly Archives: 2025

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

Nikunj Hatkar 10:53 am on September 10, 2025
Tags:   

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

Krupa Nanda 6:25 am on September 8, 2025
Tags:   

Week in Test: September 08, 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:  Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

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

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/index.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 🎉

@mosescursor was assigned a test contributor badge!

Read/Watch/Listen 🔗

  • Last chance to nominate the test 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. : Test Team Reps: Call for Nominations Voting will begin soon!
  • 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.6 RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. is ready to download.
  • Introducing the #content-creators slack channel
  • WordPress 6.9 Development Cycle

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

Olga Gleckler 7:51 pm on September 2, 2025
Tags: ,   

X-post: Test Team Update: 2 September, 2025

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

Moses Cursor Ssebunya 5:46 am on September 2, 2025
Tags: ,   

Test Chat Summary: August 28th, 2025

On Thursday, August 28, 2025 at 07:00 PM GMT+3, <test-chat> started in #core-test facilitated by @mosescursor The agenda can be found here.

1. Attendance

@sirlouen @callumbw95 @krupajnanda @iamshashank @oglekler  @dilip2615 @getsyash @nikunj8866 

2. Volunteer

This week’s Note-taker was @mosescursor
Meet next week’s note taker @nikunj8866 

3. Announcements

4. Test Team Updates

Appreciations to the 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/ Table Leads at 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. US 2025 especially the Remote Leads.

5. Focal Group Updates

6. Test Team Discussion, Questions, and Blockers

  • Follow up on the proposal for the TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Test Reports.

6.1 Change of the time for the Contributor Session – Sessions have been moved 1 hour ahead and this change has been updated in the meeting calendar. Next meeting will be on Thursday at 2PM GMT instead of the regular Thursday at 1PM GMT

6.2 Ticket Review Discussion

  • The team did not have time to fully review the ticket reports; this topic will continue next week.
  • There was some uncertainty expressed about the Needs Reproduction report — specifically, how it should be presented and structured.
  • Concern was raised about applying the Future Milestone tag too early, as it may feel premature in some cases.
  • Clarification:
    • Future Milestone is only for tickets that are already confirmed as valid and worth pursuing.
    • Ideally, one committer or maintainer should check in on a ticket before it gets this tag.
    • Currently, there is no alternative tag besides Future Milestone that signals such validation.

6.3 Meeting Notes – Permissions & Moderation

  • Request: @SirLouen suggested asking for more permissions on the Test P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org (for himself, @krupajnanda, and possibly @oglekler) to help moderate comments to avoid possible spam comment. (This is based on the recent observation on this post)
  • Agreement: @krupajnanda noted this is much needed and will check with #meta.
  • The Vote: voting was concluded with 7 votes in favour and 0 votes against as evidenced here

7. Open Floor

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

8. Next Test Team Sessions

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

#core-test

Krupa Nanda 7:04 am on September 1, 2025
Tags:   

Week in Test: September 01, 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: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

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/index.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:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

2025 Schedule:

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

#core-test

Moses Cursor Ssebunya 1:16 pm on August 28, 2025
Tags:   

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

Krupa Nanda 10:11 am on August 25, 2025
Tags:   

Week in Test: August 25, 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: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

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 to the Test Team are also a fantastic way to level up your WordPress knowledge and skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

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/index.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:

Profile Badge Awards 🎉

Profile badge is awarded to @getsyash!

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

2025 Schedule:

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

#core-test

Krupa Nanda 6:23 am on August 25, 2025
Tags: , ,   

Core Test Team at WCUS 2025 Contributor Day

Hello WordPress enthusiasts 👋

Join us for Contributor Day at WCUS 2025 on Tuesday, August 26, in Portland, Oregon! It’s a day full of learning, teamwork, and real impact. The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Team will be there with open arms, whether you’re a first-time tester or already know your way around a bug report. Come and be part of something awesome and help make WordPress even better. Here’s a sneak peek at what we have planned for the Core Test Team and how you can get involved.

🎯 Core Test Team Goals

Our focus for the day revolves around achieving meaningful and ambitious contributions.

  • Onboard New Contributors: Provide guidance and mentorship to newcomers eager to join the Core Test Team.
  • Help with tickets that need testing:
  • Expand Automated Testing Coverage: Increase the number of automated tests for core components.
  • Test bugs or features and report new issues.
  • Improve Documentation: Enhance the clarity and comprehensiveness of testing guidelines.
  • Triage Issues: Review and prioritise open tickets.

Contributors with different skills, talents, and backgrounds can get involved in a variety of ways. If you are unsure how to start or what to do, give it a try. Table leads and experienced contributors will help you get started. You are welcome! 🙌🏻

🌐 Collaboration and Community

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/ at WCUS 2025 won’t just be about contributing tests; it’ll be about building connections and celebrating community. In a spirit of collaboration, contributors will share ideas, support one another, and recognise each other’s wins. The energy and enthusiasm will be contagious, reinforcing the shared purpose that unites the WordPress community.

If you are new to core test contributions and want to stay updated on what’s happening, please join the #core-test channel. 

🗓️ We have team meetings and Triage sessions on an alternating basis every Wednesday at 16:00 UTC.

🗓️ We also have weekly coffee sessions every Thursday, at 13:00 UTC

👤 Meet the Test Team Table Leads

We’re thrilled to introduce our Test Team Table Leads for WCUS 2025. They are dedicated individuals will be guiding and supporting contributors throughout the day:

In-Person Table Leads:

Online (Remote) Table Leads:

Their drive and knowledge will inspire everyone to contribute their best and make a real difference.

🔗 Helpful Resources

To make the most of Contributor Day, take a moment to explore these resources beforehand so that you can dive straight into the exciting work when you arrive at the venue!

👀 Looking Ahead

As we prepare for this Contributor Day, we look forward to the progress and innovation that these contributions will bring to the WordPress project. We encourage everyone who plans to participate to stay engaged and keep the momentum going. Your contributions, whether big or small, make a significant impact.

Thank you in advance to all the contributors who will join us in Portland and those who will participate remotely. Together, we’re making WordPress better. 💪

Interested in Contributor Day, but not sure if Test is the right fit for you? Try out Make WordPress’s Find Your Team tool to discover right opportunities that may interest you.

Props to @oglekler for peer review of this post. 🙌

#contributor-day, #core-test, #wcus

Krupa Nanda 9:58 am on August 20, 2025
Tags:   

Week in Test: August 18, 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: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

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/index.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:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

2025 Schedule:

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

#core-test