Week in Test: April 29, 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: 28 April 2025

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

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

Test Chat Summary: April 23, 2024

On Thursday, April 23, 2025 at 12:00 AM GMT+8, <test-chat> started in #core-test facilitated by @pavanpatil1. The agenda can be found here.

Attendance

@sirlouen @krupajnanda @pavanpatil1 @zeelthakkar @oglekler @pratiklondhe (async) @muddassirnasim(async) @nikunj8866 (async) @narenin (async)

2. Volunteer

This week’s Note-taker and facilitator:

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

  • No updates

6. Questions/Blockers

  • No Questions/Blockers reported in this meeting

7. Call for Testers/Visibility

  • WordPress 6.8 is already out. If you come across any issues, please report them on Core Trac or GitHub.
  • 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/ 20.7 is now available – https://wordpress.org/plugins/gutenberg/

8. Discussion

During the meeting, @sirlouen raised the issue of the Workflow Keywords, specifically around the keyword needs-testing-info, which has been causing confusion due to its similarity with needs-testing.
Two solutions were proposed, with the renaming of the keyword considered the most viable. Here, the objective is to enhance usability and maintain clarity in the keyword naming scheme. @joemcgill suggested the keyword needs-test-info, as it aligns better with the current format of existing workflow keywords.

A quick poll was conducted during the meeting, and the majority voted for the following naming convention:

  • needs-test-info
  • has-test-info

These changes will align testing-related keywords with the overall naming scheme used in the project.

@krupajnanda asked whether the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team would support implementing these changes once the updated keywords and their intended usage are shared. @joemcgill confirmed his willingness to assist with this.

@sirlouen mentioned that once @muddassirnasim completes the meeting notes, he will forward the information to @dd32 for inclusion in the official TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. documentation.

9. Open Floor

No items discussed

10. Next Meeting 🗓

April 30, 2025, at 21:30 GMT+5:30: <test-triage> #core-test

May 07, 2025, at 21:30 GMT+5:30: <test-chat>  #core-test!

#core-test, #meeting-notes

Team Chat Agenda: April 23, 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 23rd April 2025 at 16:00 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.

Week in Test: April 21, 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/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 🎉

Profile badges awarded to Manoj Maharrshi

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

Test Chat Summary: 10th April 2025

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

1. Attendance 

@muddassirnasim @sirlouen @krupajnanda @oglekler @ravigadhiyawp @pbearne @sumitbagthariya16 @mukesh27 @indirabiswas27 @pavanpatil1 @mkrndmane @pratiklondhe @narenin @mebo (async) @nikunj8866 (async) @vaibhavsweb (async)

2. Volunteer 

For the next bi-weekly chat –

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

  • We are in a 6.8 release cycle and only a week from our final release. WordPress 6.8 is going to be released on April 15, 2025
  • Check what to expect in WordPress 6.8 release: Roadmap to 6.8

6. Questions/Blockers

@Muddassir Nasim reported successful testing using 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. Tester 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, expressed interest in learning WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/, and showed a willingness to explore interactive testing through CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress..

  • @Krupa Nanda suggested testing via WP-CLI and directed Muddassir to @Makarand Mane for further guidance.
  • @Makarand Mane reaffirmed his availability to support WP-CLI testing and offered assistance proactively.
  • @Manuel Camargo sought clarification on the scope of Nasim’s interest, distinguishing between WP-CLI specific testing and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. testing.

@Olga Gleckler encouraged to test the site with real and data, if you have this opportunity. So, if you can test on a staging site close to what you have on production (not on production, of course). Becasue some things can only happen in certain circumstances and conditions.

7. Call for Testers/Visibility

8. Open Floor

@krupajnanda suggested @SirLouen to prepare a draft for the suggestion and feedbacks he added here and mentioned once thr post will be ready we can post it in the community for feedback. 

9. Next Meeting 🗓

The next meeting will be on Wednesday, April 23, 2025, at 12:00 AM GMT+8 , held on #core-test!

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!

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

#meeting-notes 

#core-test