Highlighted Posts

Categorize a post as Highlight to add it to this section.

X-post: Test Team Update: 10 February 2025

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

Week in Test: February 10, 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:

6.8 Related issues need testing

The following 6.8 tickets need testing those are having 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

Core Test Team at WCAsia 2025: Contributor Day

Hello WordPress enthusiasts 👋

We’re gearing up for an exciting Contributor Day at WordCamp Asia (WCAsia) 2025, set to take place this month in the vibrant city of Manila, Philippines! This annual gathering of WordPress enthusiasts brings together a diverse group of contributors to collaborate, learn, and significantly impact the WordPress project. 

Here’s a sneak peek at what we have planned for the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Team and how you can get involved.

🕰️ Important Times to Note: (All the times are mentioned in PHT)

🎯 Core Test Team Goals

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

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 Day at WCAsia 2025 will not just be about work; it will also be about building connections and fostering community spirit. The collaborative atmosphere will be real, with contributors exchanging ideas, offering help, and celebrating each other’s successes. The energy and enthusiasm of the participants will be truly inspiring, reinforcing the sense of belonging and shared purpose within 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.

👩🏻‍💻 Meet the Test Team Table Leads

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

In-Person Table Leads:

Online (Remote) Table Leads:

Their expertise and enthusiasm will be invaluable in ensuring a productive and engaging Contributor Day for all participants.

🔗 Helpful Resources

To ensure you get the most out of Contributor Day, please review the following resources before the event so that you can focus on the fun stuff when you arrive:

👀 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 Manila 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 other opportunities that may interest you.

Props to @oglekler and @ankit-k-gupta for peer review of this post. 🙌

#wcasia2025, #core-test

X-post: Test Team Update: 3 February 2025

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

Week in Test: February 3, 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:

6.8 Related issues need testing

The following 6.8 tickets need testing those are having patches:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

  • We are currently in the WordPress 6.8 release cycle. Read more about the release squad, timeline, and focus for this release.
  • ⚠️ 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 is only five weeks away!
  • WordPress 6.7.2 is scheduled for February 11, with an RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. planned for February 4. Review the next minor release milestone.
  • The next 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/ release will be 20.2, tentatively scheduled for February 5. It will include the following issues.

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: 29th January 2025

On Wednesday, January 29, 2025, at 07:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@krupajnanda, @huzaifaalmesbah, @oglekler, @kausaralm, @sumitbagthariya16, @narenin, @dhruvang21, @pavanpatil1, and @lumiblog

2. Looking for Volunteer

  • February 12: Test Chat Meeting Facilitator – Volunteer Needed 
  • February 12: Test Chat Meeting Recap Notes – Volunteer Needed
  • Remote Table leads for WCAsia. Please check this guide for more details on what to expect as a Test Table Lead.
  • A volunteer to work on Call for testing WordPress 6.8 release. For more details, check out the guide: How to Facilitate a Call for Testing

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

The members reported no updates.

6. Questions/Blockers

No questions/blockers were reported by the members.

7. Open Floor

There was no issue to discuss. 

8. Next Meeting 🗓

The next meeting will be on Wednesday, February 12, 2025, at 07:00 PM GMT+3, held on #core-test!

#meeting-notes

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!

#summaries

Team Chat Agenda: 29th January 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 29 January 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
  • Looking for volunteers
    • Facilitator and note taker for the next bi-weekly chat
    • Remote Table leads for WCAsia. Please check this guide fore more details on what to expect as Table Lead.
    • To work on Call for testing WordPress 6.8 release. For more detail, check out the guide: How to facilitate a Call for Testing
  • Announcements
  • Test Team Announcements
  • 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.

#agenda, #core-test

X-post: Test Team Update: 27 January 2025

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

Week in Test: January 27, 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 📣

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.8 Related issues need testing

The following 6.8 tickets need testing those are having 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

X-post: Test Team Update: 20 January 2025

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