X-post: Test Team Update: 7 April 2025

X-post from +make.wordpress.org/updates: Test Team Update: 7 April 2025

Week in Test: April 07, 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 posts highlight features and releases that need special attention:

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:

  • No tickets found

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

  • WordPress 6.8 RC2 is now available for testing. Please share your feedback and report the issue on tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/./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/ if you find any regression.
  • The Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 3 release of WordPress 6.8 will be available on Tuesday, April 8, 2025 Please check the detailed overview of the release schedule for WordPress 6.8. Join the Release Party in #core to test and provide the feedback!
  • The Gutenberg 20.6 is released and ready for testing.
  • WordPress 6.8 Field Guide
  • New REST API Filter for Exposing Menus Publicly in WordPress 6.8
  • Dotorg Core Committers Check In

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

X-post: Test Team Update: 31 March 2025

X-post from +make.wordpress.org/updates: Test Team Update: 31 March 2025

Week in Test: March 31, 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 posts highlight features and releases that need special attention:

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:

  • No tickets found

Profile Badge Awards 🎉

SirLouen and Praful

Read/Watch/Listen 🔗

  • WordPress 6.8 RC1 is now available for testing. Please share your feedback and report the issue on tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/./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/ if you find any regression.
  • The RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 2 release of WordPress 6.8 will be available on Tuesday, April 1, 2025.. Please check the detailed overview of the release schedule for WordPress 6.8. Join the Release Party in #core to test and provide the feedback!
  • WordPress 6.8 Field Guide
  • The new version of the 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/ 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 now available in our plugin directory
  • Gutenberg 20.6 is scheduled for release on WednesdayApril 2, 2025

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

Test Chat Meeting Recap Notes: 26 March 2025

1. Attendance

krupajnanda, nazmul111, pmbaldha, shanemuir, kausaralm, vgnavada, pavanpatil1, hage, oglekler, sirlouen, narenin

2. Looking for volunteers

  • Note Taker – Needs volunteer
  • Next meeting facilitator – Needs volunteer

3. Announcements

  • Call for testing post is out. Please help test WordPress 6.8
  • RC1 release of WordPress 6.8 is now available.
  • The RC2 release of WordPress 6.8 is scheduled for the 1st of April. Please check the detailed overview of the release schedule for WordPress 6.8. Join the Release Party 1st April @5PM CEST in #core to test and provide the feedback.
  • 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/ 20.5 was released on Thursday, March 20th. Checkout the milestone for the issues that were part of the 20.5 release.

4. Test Team Announcements

5. Focal Group Updates

6. Questions/Blockers

  • SirLouen first raised the recurring issue about the lack of a place for test team members to comment on improvement ideas and proposed a solution to use the following site to add ideas and comments for future meetings. You can see the topics without registering, but if you want to propose new topics, you can send a direct message to @SirLouen on the Slack server with an email address to add you.
  • Krupa proposed another additional approach to add ideas for next meetings: A thread will be opened 2 days before each meeting in the #core-test Slack channel, and you can add your ideas there.

7. Call for testers/visibility:

8. Open Floor

  • SirLouen first raised an issue about the testing workflow implementation gap, insufficient test reports, QA concerns and a lack of a stable testing team, and proposed a solution: Introducing an unofficial mentorship program to help new contributors get involved in testing more details here, with the primary goal of building a stable testing team that could be referenced similar to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, editor team, or performance team.
  • OGlekler noted that testing is being promoted in Core Contributor meetings and suggested promoting testing in other places as well. We will do a brainstorming session to discuss this. Here is a thread to brainstorm the ideas. Also mentioned that the previous success with the Contributor Mentorship Program came from social media promotion, and pointed out the challenge with gaining volunteer motivation and commitment over time.
  • Krupa acknowledged the need for a structured testing workflow and a stable team, but volunteer participation can be a challenge and the suggested mentorship program had potential to be a stepping stone for new contributors to get involved in testing. More insights are needed to ensure proposed changes are both sustainable and practical.

9. Next Meeting

10. Meeting Wrap up

SirLouen will help to develop a roadmap for progressive improvements to the testing workflow, with a focus on building a reliable testing team as the first priority.

We encourage you to participate in any of the ways available, Slack #core-test channel, with a comment in this post, directly in the next meeting or adding up to the Shared Doc Notes commented in this post.

Props to krupajnanda for peer reviewing this meeting recap.

Team Chat Agenda: 26th March 2025

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, March 26, 2025 at 05:00 PM GMT+1, which will be held in the #core-test Slack channel. Lurkers welcome!

Agenda

1. Attendance

2. Note-taker and facilitator selection for the next meeting

3. Announcements

  • Call for testing post is out. Please help test WordPress 6.8
  • RC1 release of WordPress 6.8 is now available.
  • The RC2 release of WordPress 6.8 is scheduled for next Tuesday, April 1st. Please check the detailed overview of the release schedule for WordPress 6.8. Join the Release Party in #core to test and provide the feedback!
  • 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/ 20.5 was released on Thursday, March 20th. Checkout the milestone for the issues, those were part of the 20.5 release.

4. Test Team Announcements

5. Focal Group Updates

6. Questions/Blockers

7. Call for testers/visibility:

8. Open Floor

  • Got a topic? Add in comments below, or mention it 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?

#core-test

Week in Test: March 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: 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 posts highlight features and releases that need special attention:

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:

  • Same as above tickets

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

  • WordPress 6.8 Beta 3 is now available for testing. Please share your feedback and report the issue on tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/./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/ if you find any regression.
  • The RC1 release of WordPress 6.8 is scheduled for Tuesday, March 25th. Please check the detailed overview of the release schedule for WordPress 6.8. Join the Release Party in #core to test and provide the feedback!
  • What’s new for developers? is live now!
  • 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/ 20.5 was released on Wednesday, March 19th. This is the first version of Gutenberg to be merged into WordPress 6.9 next major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. of the this year. Checkout this milestone for Gutenberg 20.5 release related updates.

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

X-post: Test Team Update: 24 March 2025

X-post from +make.wordpress.org/updates: Test Team Update: 24 March 2025

X-post: Test Team Update: 17 March 2025

X-post from +make.wordpress.org/updates: Test Team Update: 17 March 2025

Test Chat Summary: March 12, 2025

On Wednesday 12 March 2025 at 21:30 GMT+5:30, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance

@Krupajnanda, @oglekler, @sirlouen, @vgnavada, @kausaralm, @shiponkarmakar, @pavanpatil1, @narenin, @nikunj8866, @pmbaldha, @mukesh27

2. Looking for Volunteers

  • @vgnavada volunteered to take notes on this meeting.

3. Announcements

  • Call for testing post is out. Please help test WordPress 6.8
  • Beta 2 release of WordPress 6.8 is now available for testing.
  • 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. 3 release of WordPress 6.8 is scheduled for next Tuesday, March 18th. Please check the detailed overview of the release schedule for WordPress 6.8.  Don’t miss the Release Party in #core to test and provide feedback! :dart:
  • 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/ 20.4 was released on Wednesday, March 5th. Check out the milestone for the issues that were part of the 0.4 release.

4. Test Team Updates

5. Focal Group Updates

  • We are in the 6.8 release cycle and only 2 weeks from our first RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. release.
  • Check out what to expect in the WordPress 6.8 release: Roadmap to 6.8

6. Questions/Blockers

@sirlouen questioned about the testing suggestions doc: https://docs.google.com/document/d/1Q7Kzs-78XvrAjnjG_MhBJR6bSBk80rvzwnV90iYTjhg/edit?tab=t.0

7. Call for testers/visibility

8. Open Floor

The discussion started with an invitation for participants to share thoughts or raise topics for discussion. New contributors were directed to the bookmarks folder in the channel for helpful resources.

Key Points Discussed:

  1. Addressing Ethical Practices in Testing:
    • @vgnavada: Highlighted the issue of copying someone else’s test case, including the exact screenshot and text copy, and presenting it as their own, pointing out the unethical nature of this practice.
    • @sirlouen: Stated that the other user likely reused the same steps to confirm the patch without taking the time to do the work again from scratch. He described this as poor testing practice, as it would have been better to try different approaches to expand the testing cases.
    • @oglekler: Acknowledged that such issues hadn’t been caught before but noted that it should be looked into now. While copying someone else’s work is demotivating, She reassured that it wouldn’t benefit the person doing it and advised not to worry too much about it.
    • @krupajnanda: Expressed understanding of the concern and emphasized that copying someone else’s work, especially when it involves significant effort, is not the right way to contribute. She suggested that more eyes should be on each ticket to offer different perspectives and solutions.

  2. Bridging the Gap: Improving Collaboration Between QA and Development Teams
    • Challenges Identified: @sirlouen mentioned the often it observed that patches get approved with minimal verification, which can lead to unexpected issues down the line. When tickets don’t clearly outline use cases, it can slow down testing and create confusion. We need a clear mechanism for this situation to be resolved.
    • Proposed Solutions: Introduce a needs-use-cases tag to ensure clear reporting and smoother testing to encourage detailed testing reports and context from committers.
    • Next Steps: @mukesh27 supported the ideas and suggested a blog post to drive awareness and change.

9. Next Meeting 

10. Closing Remarks

The meeting wrapped up with a reminder to participants that discussions and questions are always welcome in the Test Team channel. The community is encouraged to continue contributing and collaborating outside of scheduled meetings.

  • @krupajnanda thanked @sirlouen for their feedback and assured them that the team would work on resolving the gaps identified. She acknowledged the active participation of the team during the meeting and emphasized that team members can raise questions or start discussions anytime in the Test Team channel.

Takeaways

The main takeaway is that better teamwork, clear communication, and accountability between QA and development teams are key to success. When both sides work together with honesty, transparency, and shared responsibility, things run more smoothly and lead to better results.

Thank you, @krupajnanda, for the peer review and for helping me write this post. 

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#core-test, #summaries