Yearly Archives: 2025

Krupa Nanda 4:58 am on May 12, 2025
Tags:   

Test Chat Summary: May 07, 2025

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

1. Attendance

@krupajnanda @muddassirnasim @pavanpatil1 @oglekler @sirlouen @SJ @kausaralm @lumiblog(asnyc) @narenin(asnyc) @puja

2. Volunteer

This week’s Note-taker and facilitator:

3. Announcements

4. Test Team Updates

5. Focal Group Updates

  • #core-editor team has shared this for the issues that needs testing. Please feel free to pick and contribute to any tickets and make sure to update the same in the #core-editor for the better visibility.
  • @sirlouen shared an update to the team that the new keyword has already been updated. Reports containing the old keyword will not be automatically updated and will need to be revised manually. He also mentioned that if any old keywords will be encountered then he will handle that part.
  • SirLouen requested @OGlekler to remove the -needs-testing-info keyword from the weekly reports.
  • The new list of keywords to use is: needs-testing has-patch -dev-feedback -2nd-opinion -close -needs-refresh -needs-design -needs-design-feedback

6. Questions/Blockers

@sirlouen raised a concern that many test reports genuinely needing attention are being overlooked, while others are already tested number of times but are still being retested which indeed does not add any value. To address this, he proposed manually curating a list of reports that actually need testing and will share clear, straightforward testing instructions to help non-technical testers contribute effectively.

In response, @krupajnanda thanked @sirlouen for volunteering to curate the list and requested that the list be posted in the channel once ready, so it can be pinned and easily accessed by others. (The list has already been pinned)

7. Call for Testers/Visibility

8. Open Floor Discussion

In a recent discussion, @sirlouen proposed a new initiative to host public Patch Test Scrub sessions dedicated to testing patches. Participants will be able to:

  • Join a scheduled session and test patches live alongside others.
  • Ask questions and get real-time guidance especially for more complex patches.
  • Learn from practical examples pulled from SirLouen’s Curated Testing List.

The very first Patch Test Scrub is scheduled for Monday, May 12th at 3PM GMT (5PM CEST / 8:30PM IST) and will be facilitated by @sirlouen. Future scrubs may adapt based on feedback and participation that we will receive.

9. Next Meeting

Wednesday, 14 May 2025 at 21:30 GMT+5:30:  <test-triage> in #core-test.

Wednesday, 21 May 2025 at 21:30 GMT+5:30:  <test-chat> in #core-test.

#core-test

Krupa Nanda 7:08 am on May 7, 2025
Tags:   

Team Chat Agenda: 7th May 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 07 May 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 – @muddassirnasim
    • This week’s note-taker is – Looking for a volunteer
  • Announcements
  • Test Team Announcements
  • Focal Group Updates
    • We are waiting for updates regarding the newly proposed keyword from #core team. A detail about the same can be found here under Discussion section.
  • 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

Olga Gleckler 5:37 am on May 6, 2025
Tags: ,   

X-post: Test Team Update: 5 May, 2025

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

Krupa Nanda 10:44 am on May 5, 2025
Tags:   

Week in Test: May 05, 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 from 6.8.2 need PHPUnit tests built to accompany their respective patches:

  • No tickets found

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

Krupa Nanda 6:44 am on April 29, 2025
Tags:   

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

  • 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

Olga Gleckler 8:21 pm on April 28, 2025
Tags: ,   

X-post: Test Team Update: 28 April, 2025

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

Krupa Nanda 6:28 am on April 27, 2025
Tags: ,   

Test Chat Summary: April 23, 2025

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

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

Pavan Patil 11:23 am on April 23, 2025  

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.

Olga Gleckler 8:32 pm on April 21, 2025
Tags: ,   

X-post: Test Team Update: 21 April 2025

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

Olga Gleckler 8:32 pm on April 21, 2025
Tags: ,   

X-post: Test Team Update: 21 April 2025

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