Nikunj Hatkar 1:14 pm on July 16, 2026
Tags: ,   

Team Chat Agenda: 16th July, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 16 July 2026, 03: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.

#test-chat-agenda

Nikunj Hatkar 4:17 am on July 6, 2026
Tags: , ,   

Test Scrub Schedule for WordPress 7.1

As you’re aware, WordPress 7.1 is slated to be the next major release of 2026, with the official release date set for August 19, 2026. As we gear up for this important milestone, our Test team will be shifting gears a bit.

Starting from our upcoming weekly Patch Testing Session, we’ll be running a Test Scrub for WP 7.1 instead of the usual Future Milestone Tickets. These scrubs will focus specifically on tickets and issues related to the WordPress 7.1 milestone. It’s a great opportunity to contribute to this 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. and make a tangible impact on the final product.

Test Scrub in Place of Patch Testing Sessions

Starting from our next scheduled session, we’ll be running Test Scrubs on the 2nd and 4th Thursday of each month at 3:00 PM UTC. These sessions will focus specifically on the WordPress 7.1 milestone tickets.

Where Will It Happen?

Each Test Scrub will take place in the #core-test channel on the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ at the same time as our regular weekly Test team meetings. If additional release-focused scrubs are scheduled, they’ll also be announced in #core-test and added to the meetings calendar.

What Tickets Will We Focus On?

We’ll primarily concentrate on tickets that are tagged Has Patch or Needs Testing for the 7.1 milestone. You can find these tickets in the 7.1 report on Trac. As the release moves through 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. and RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge., we’ll also highlight key features and regressions that need focused testing.

Interested in Leading a Test Scrub?

Did you know that anyone can lead a Test Scrub at any time? Yes, that means you can!

If you’re interested in leading a scrub, please reach out in the #core-test Slack channel with:

  • The day and time you’re considering
  • The report or tickets you’d like to focus on (for example, a specific TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. report, a feature area, or a Beta/RC build)

If you’re planning a scrub that’s specifically focused on WordPress 7.1, that’s fantastic! We can add it to our schedule so the rest of the team knows to join in. Leading a scrub is a great way to contribute.

Let’s Contribute Together

This is a perfect chance to get involved with the major release of WordPress 7.1, learn more about the release process, and help ensure the quality and stability of WordPress. Your contributions will make a difference, so join us for the Test Scrub sessions and be a part of this exciting release.

Thank You ❤️

Thanks to everyone contributing time, testing, feedback, and expertise. Community testing plays a critical role in making each WordPress release successful.

Let’s work together to make WordPress 7.1 a smooth and high-quality release.

Props to @amykamala, @krupajnanda, and @huzaifaalmesbah for pre-publish review.

#7-1, #call-for-testing, #core

Moses Cursor Ssebunya 1:34 pm on July 2, 2026
Tags: , , ,   

Month in Test: July 02, 2026

Hello and welcome to another edition of Month 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.

Table of Contents

  1. Calls for Testing 📣
  2. Test Handbook📘
    1. Merging of Test Handbook in Github
  3. Weekly Testing Roundup 🤠
    1. 1. WordPress Core Testing
      1. a. Patch Testing 🩹
      2. b. Bug Reproduction
      3. c. Test Team Issues
    2. 2. Gutenberg Testing
      1. a. Gutenberg Bug Reproduction Testing
      2. b. Gutenberg Patch Testing
  4. Profile Badge Awards 🎉
  5. Read/Watch/Listen 🔗
  6. 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:

Test Handbook 📘

Merging of Test Handbook in 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 by the repository owner. https://github.com/

For the last few weeks, a good number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.

  • We want to inform that the Test Handbook is officially synced. There might be a couple of bugs and things that are not looking good pending to be fixed.
  • Feel free to give it a check here, and if you find any bugs, go to the GitHub repository and report them.
    • You can send a PR with the fix, or simply send the issue, and we will check it

Weekly Testing Roundup 🤠

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

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Testing

a. 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 (13) 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:

b. Bug Reproduction

It is necessary to confirm if the bug is happening under multiple conditions and environments, using the bug reproduction report in order to validate the issue.

The following tickets (135) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, then provide a bug reproduction report:

c. Test Team Issues

Here are the current activities being discussed in the Test Team Github:

  1. We need to review the Test Team Issues. If you have a possible solution, comment in the Issue or submit a PR.

2. 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/ Testing

👋Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets (18) have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

b. Gutenberg Patch Testing

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 (0) 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:

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
    • Weekly Patch Testing Scrub: Second and Fourth Thursday of the Month at 15:00 UTC
    • Weekly Test Chat: Third Thursday of the Month at 15:00 UTC
    • Monthly Voice Test Chat: First Thursday of each month at 15:00 UTC
  3. Call for Testing

Upcoming Meetings 🗓

🚨There will be regular #core-test meetings. The schedule is being worked on and final schedule will be shared after finalizing the discussion

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

props to @nikunj8866 for peer reviewing this post

#core-test, #fse-outreach-program, #gutenberg, #make-wordpress-orgupdates

Nikunj Hatkar 1:25 pm on June 22, 2026
Tags: , ,   

Test Chat Summary: June 18th, 2026

On Thursday, 18 June 2026, 03:00 PM UTC, <test-chat> started in  #core-test facilitated by @nikunj8866. The agenda can be found here.

1. Attendance

In attendance was:
@nikunj8866 @ozgursar @huzaifaalmesbah @r1k0 @Jadavsanjay @pavanpatil1 @juanmaguitar @mosescursor

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

  1. Weekly Testing Digest failed
    • Reported that this week’s Weekly Testing Digest workflow failed to run, sharing the failed run for reference and noting a recently merged PR #172 that touched the file, in case it was related.
    • @huzaifaalmesbah suggested creating a 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 by the repository owner. https://github.com/ issue to track and investigate the failure, noting the workflow may need to install the required Playwright browsers before running the digest script.
    • @ozgursar shared the error message, which indicated the Playwright Chromium executable was missing on the runner (chrome-headless-shell not found).
    • @r1k0 felt the merged PR was not the cause and suspected the cached browser instead, agreeing with @ozgursar that updating the Playwright version might resolve it. He offered to investigate in depth and noted the workflow should be updated to prevent this from recurring.
    • @nikunj8866 created issue #177 to track the failure, inviting further comments there.
  2. Recognize WordPress 7.0 Test Contributors – Badge Awards & Blog Post
    • @nikunj8866 noted this was discussed in the last voice chat, but with the 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. event fewer members could join, so it was revisited. He shared his thoughts on issue #174 and invited input.
    • @huzaifaalmesbah suggested not waiting too long on the blog post since the 7.1 release squad has already been announced – publishing it if everyone agrees, or otherwise revisiting a similar recognition effort during the 7.1 release cycle.
    • @nikunj8866 agreed and asked @mosescursor for his opinion on the blog post.
    • @mosescursor confirmed he would take a look.
  3. Proposal: Building a Test Chat and Bug Scrub Facilitator Plugin
    • @r1k0 tested the 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. and found it really great.
    • @nikunj8866 shared his view that a plugin is a better approach than a website, as it keeps everything within the WordPress ecosystem and is easier for the team to maintain and use. He suggested documenting the plugin’s details on the Test Chat Moderator Guide handbook page, and adding a live preview link so clicking a button opens WordPress Playground with the plugin already installed for instant testing. He invited everyone to share their thoughts on issue #165.
  4. Provide structured guidance for Core Trac ticket reports
    • @nikunj8866 suggested that issue #116 might be better handled by the MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team – either by raising it in #meta or by creating a ticket in the Meta Trac.
    • @r1k0 agreed and offered to open it in the Meta TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/., with the GitHub issue closed as not planned.
  5. Proposal: Restructure Test Handbook to Support Multiple Testing Domains

4. Open Floor

There were no additional topics raised during the open floor session.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

#core-test, #test-chat-summary

Nikunj Hatkar 1:00 pm on June 18, 2026
Tags: ,   

Team Chat Agenda: 18th June, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 18 June 2026, 03: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.

#test-chat-agenda

Nikunj Hatkar 1:00 pm on June 9, 2026
Tags: ,   

Test Team Voice Chat Summary:: 4th June, 2026

Voice Chat notes: 6/4/26 in #core-test slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ AI took notes for this huddle from 1:02:57 AM – 1:35:04 AM GMT+10. Test team discussed PR reviews, a facilitator 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. proposal, contributor badge criteria, and upcoming WordPress ecosystem announcements and testing opportunities. View huddle in channel

Attendees

@nikunj8866, @ozgursar, @Mohammed Kateregga, @SAndrew, and @Kamran Abdul Aziz

🌟 Summary

  • Testing Digest PR: Patch Version Milestones
    • @nikunj8866 and @ozgursar lack familiarity with the workflow automation involved in this PR. [10:07] [10:15]
    • @nikunj8866 identified Enrico and Junema as better suited to review the PR due to their involvement with the automated workflow. [10:28]
    • @ozgursar explained the workflow uses 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 by the repository owner. https://github.com/ Actions to scrape test results, summarize them, and push to Slack. [10:29] [10:50]
  • Chat and Bug Scrub Facilitator Plugin
    • @nikunj8866 reviewed the plugin and agrees it is the best option compared to a separate web page. [11:31] [11:39]
    • @ozgursar stored messages in a JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. file rather than hardcoding in 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 to allow easy editing and customization. [11:49]
    • Copy-pasting plugin content to Slack loses formatting (backticks for usernames); manual editing is required to restore formatting. [12:15] [12:47]
    • @ozgursar already linked a WordPress Playground preview in the GitHub issue for direct testing without hosting. [13:59] [14:21]
    • @nikunj8866 suggested adding plugin details to the chat moderator guide handbook page. [13:28]
  • WordPress 7.0 Test Contributors Badge Awards
    • @nikunj8866 reviewed the proposal and confirmed the criteria requirement: contributors must submit 5 test reports to qualify. [17:37] [18:01]
    • Badge assignment cannot be automated; the system only allows accepting or rejecting requests, not directly adding badges to profiles. [18:10] [18:42]
    • @ozgursar suggested announcing the 7.0 test contributors and allowing people to request badges themselves after seeing the announcement. [19:15]
    • @nikunj8866 will review a draft blog post and discuss it with Moses before finalizing. [19:31]

🗣️ Announcements

This Slack Bot uses AI to generate notes, so some information may be inaccurate. They’re based on the huddle transcript and thread and can be edited anytime.

Props to the Slack Bot that helped make the summary.

#test-chat-summary

Nikunj Hatkar 1:33 pm on June 5, 2026
Tags:   

Month in Test: June 05, 2026

Hello and welcome to another edition of Month 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.

Table of Contents

  1. Calls for Testing 📣
  2. Test Handbook📘
    1. Merging of Test Handbook in Github
  3. Weekly Testing Roundup 🤠
    1. 1. WordPress Core Testing
      1. a. Patch Testing 🩹
      2. b. Bug Reproduction
      3. c. Test Team Issues
    2. 2. Gutenberg Testing
      1. a. Gutenberg Bug Reproduction Testing
      2. b. Gutenberg Patch Testing
  4. Profile Badge Awards 🎉
  5. Read/Watch/Listen 🔗
  6. 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:

Test Handbook 📘

Merging of Test Handbook in 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 by the repository owner. https://github.com/

For the last few weeks, a good number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.

  • We want to inform that the Test Handbook is officially synced. There might be a couple of bugs and things that are not looking good pending to be fixed.
  • Feel free to give it a check here, and if you find any bugs, go to the GitHub repository and report them.
    • You can send a PR with the fix, or simply send the issue, and we will check it

Weekly Testing Roundup 🤠

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

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Testing

a. 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 (10) 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:

b. Bug Reproduction

It is necessary to confirm if the bug is happening under multiple conditions and environments, using the bug reproduction report in order to validate the issue.

The following tickets (139) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, then provide a bug reproduction report:

c. Test Team Issues

Here are the current activities being discussed in the Test Team Github:

  1. We need to review the Test Team Issues. If you have a possible solution, comment in the Issue or submit a PR.

2. 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/ Testing

👋Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets (7) have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

b. Gutenberg Patch Testing

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 (1) 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:

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
    • Weekly Patch Testing Scrub: Second and Fourth Thursday of the Month at 15:00 UTC
    • Weekly Test Chat: Third Thursday of the Month at 15:00 UTC
    • Monthly Voice Test Chat: First Thursday of each month at 15:00 UTC
  3. Call for Testing

Upcoming Meetings 🗓

🚨There will be regular #core-test meetings. The schedule is being worked on and final schedule will be shared after finalizing the discussion

Current 2026 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

Nikunj Hatkar 1:29 pm on June 4, 2026
Tags: ,   

Test Team Voice Chat Agenda: 4th June, 2026

Here is the agenda for the upcoming Test Team Voice Chat scheduled for Thursday, 4 June 2026, 03: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, #test-chat-agenda

Nikunj Hatkar 10:41 am on June 3, 2026
Tags: #wceu2026, ,   

Core Test Team at WCEU 2026: Contributor Day

Hello WordPress enthusiasts 👋

Tomorrow we head to Kraków. The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Team is gearing up for Contributor Day at WordCamp Europe 2026, taking place 4 June 2026 at ICE Kraków – the official kick-off to WCEU.

Testing is one of the most welcoming doors into WordPress: you don’t need to write a line of code to make a real difference, and by the end of the day you’ll have touched software used by over 40% of the web. Whether it’s your first 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/ or your fifteenth, there’s a seat for you at the Test table. Here’s what we’ve got planned and how to make the most of it.

🕰️ Schedule

All times are Central European Summer Time (CEST). Plan to arrive about an hour early to register and settle in.

  • 8:30 – Registration
  • 9:15 – Opening and welcome
  • 10:00 – Contributing to WordPress
  • 12:15 – Group photo
  • 12:30 – Lunch
  • 14:00 – Contributing to WordPress
  • 16:30 – Team summaries and wrap-up

Joining from home? Remote contributors are just as welcome – find us in the #contributor-day and #core-test channels in Make WordPress Slack.

👩🏻‍💻 Meet the Test Team Table Leads

In-Person Table Leads:

Online (Remote) Table Lead

Anukasha will be on the ground in Kraków to welcome you and get you set up, while Nimesh holds down the digital table – coordinating remote contributors and answering questions in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ throughout the day. Other Test Team regulars will be dropping by in person and online to lend a hand.

🎯 What We’ll Work On

Our focus is meaningful, achievable contributions you can make real progress on in a few focused hours:

  • Onboard new contributors. If you’ve never tested before, this is the place to start. We’ll walk you through your first test, your first triage, and your first reproduction – no prior experience needed.
  • Test core tickets that need eyes. Pick up live work straight from TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.:
  • Test the editor (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/).
  • Help test the new career functionality on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. There’s an active call for testing (feedback open through June 25) for the refreshed jobs.wordpress.net and the new career fields on WordPress.org profiles – job history, key accomplishments, and an “open to work” toggle. Try the applying-for-jobs flowFlow Flow is the path of screens and interactions taken to accomplish a task. It’s an experience vector. Flow is also a feeling. It’s being unselfconscious and in the zone. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it., browse candidates on the Jobs site, and leave feedback on the post or by opening an issue on GitHub.
  • Find a bug? File it. A clear, reproducible report on Trac is a genuine contribution in itself.
  • Improve the docs. Help sharpen the Test Team Handbook and testing guides so the next newcomer has an easier path than you did.

Bring whatever skills and curiosity you have – table leads and experienced contributors will help you find the right task. Everyone is welcome.

A gentle reminder: it’s Contributor Day, not Contribution Day. The goal is to find a meaningful way to contribute, not necessarily to land a finished patch by 16:30. Work you start tomorrow might wrap up next week – and that’s exactly how open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. is meant to work.

🌐 Collaboration and Community

Contributor Day isn’t only about the work – it’s about the people. It’s a room full of contributors swapping ideas, helping each other unstick, and celebrating small wins together. For many of us, the connections made across the Test table are what keep us coming back year after year. Come for the testing, stay for the community.

If you’d like to keep contributing after Kraków, the Test Team meets every week in #core-test. You can find the full Test Team meeting schedule and upcoming meetings here: https://make.wordpress.org/meetings/#test. Drop by any time to say hi, ask a question, or just lurk and learn.

🧰 Prepare at Home

A little setup the night before means you can dive straight into the fun stuff when you arrive. Spotty venue wifi is a fact of life, so get ahead of it:

🔗 Helpful Resources

👀 Looking Ahead

Every bug reproduced, every patch tested, and every report filed tomorrow ripples out to millions of sites. That’s the quiet power of testing: it’s unglamorous, it’s essential, and it’s how WordPress stays trustworthy release after release. We can’t wait to see what we build together in Kraków – and in Slack.

Not sure Test is the right fit? The Find Your Team tool can point you somewhere that clicks. But if you like the idea of being the person who catches the problem before a user ever does – you’ve found your table.

See you in Kraków! 💙

Props to @nimeshatxecurify for preparing and reviewing this post, and to @anukasha for the review of this post. 🙌

#wceu2026, #core-test, #wceu

Moses Cursor Ssebunya 12:41 pm on May 28, 2026  

Test Team Voice Chat Summary:: 7th May, 2026

Voice Chat notes: 5/8/26 in #core-test SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ AI took notes for this huddle from 15:01:42 – 15:58:07 UTC. The meeting covered updates and discussions on several test team initiatives, including 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 by the repository owner. https://github.com/ markdown templates, a fix for finding tickets, the ongoing handbook review, and issues with the Playground installation guide. A significant portion of the discussion focused on testing a new weekly digest workflow for Slack, and the team finalized a new alternating weekly meeting schedule. View huddle in channel

Attendees

@Moses Cursor, @ozgursar, @Huzaifa Al Mesbah, @nikunj8866, @r1k0, @Shazzad, @SAndrew, @Mohammed Kateregga, @BIGUL, @Azhar Deraiya, and @Kaushik Domadiya

🌟 Summary

  • Attendance and Introductions
  • Review/Update GitHub Markdown Test Report Templates
    • @Moses Cursor initiated a discussion to review and update the GitHub markdown test report templates, noting an issue where the existing template referenced an old report. [12:34] [14]
    • @Huzaifa Al Mesbah confirmed that he had requested the new reports be considered. [13:10]
    • @ozgursar suggested informing Yusuf about the updated test reports 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. from Sirlouen’s GitHub repository to update the markdown templates based on that. [13:43] [14:12] [14:29]
    • @Huzaifa Al Mesbah considered it a good idea but suggested creating a new issue for it, as Yusuf is a new contributor, and it might be better to handle it separately. [14:38]
    • @ozgursar agreed, noting the differences are not significant, and proposed waiting for Yusuf to make the requested changes before approving. [15:02] [15:19]
    • @Moses Cursor questioned the necessity of the current ticket if the new report already supports Markdown. [16:52] [17:32]
    • @ozgursar clarified that the combined report is archived, so Yusuf needs to work on the new one. [16:37]
    • @nikunj8866 offered to review the template once he had access to a system. [17:20]

🗣️ Announcements

This Slack Bot uses AI to generate notes, so some information may be inaccurate. They’re based on the huddle transcript and thread and can be edited anytime.

Props to the Slack Bot that helped make the summary and @huzaifaalmesbah for Peer reviewing this