Pooja Derashri 12:04 pm on March 12, 2024  

Highlighted Posts

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

Nikunj Hatkar 1:11 pm on August 13, 2026
Tags: ,   

X-post: Test Team Update: 13 August, 2026

X-post from +make.wordpress.org/updates: Test Team Update: 13 August, 2026

Moses Cursor Ssebunya 2:47 pm on August 12, 2026
Tags: ,   

Test Chat Summary: August 6th, 2026

Huddle notes: 8/7/26 in #core-test. AI took notes for this huddle from 1:02:18 AM – 1:59:19 AM GMT+10. WordPress test team reviewed four 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/ issues, closed learner pathways, assigned handbook documentation for test 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. 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 identified blockers requiring external team coordination.

Attendees

@MosesCursor, @ikamal, @huzaifaalmesbah, @ozgursar, @r1k0, @ismail0071, and @mbigul

Summary

Test Handbook Restructuring for Multiple Domains

  • @huzaifaalmesbah proposed keeping issue #111 open and splitting into sub-issues or assigning to new contributors for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. testing guidance. [30:58]
  • @ozgursar noted restructuring requires moving all current content under core directory, affecting entire handbook structure. [32:28]
  • @huzaifaalmesbah and @ozgursar agreed to start with core and 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/ directories, deferring AI and performance sections until content exists. [33:31]
  • @Moses Cursor proposed reaching out to AI and performance teams for testing content; team agreed external input is necessary before proceeding. [36:02]

Learner Pathways Issue Closure

  • @huzaifaalmesbah confirmed learner pathways look good for beginners and are ready to close. [26:16]
  • @Moses Cursor closed issue after team confirmation. [26:51]

Test Flow Plugin Documentation

  • @ozgursar reported plugin is working and ready for use via playground; only handbook documentation remains. [39:33]
  • @r1k0 suggested adding plugin documentation as a section in moderator guide rather than standalone page. [48:41]
  • @huzaifaalmesbah proposed including test report plugin and chat monitor guide in patch testing section. [53:00]
  • @ozgursar will submit plugin to WordPress directory from personal account after handbook documentation is complete. [45:08]

Team Goals and Initiatives Issue

  • @Moses Cursor noted issue #9 is unclear and suggested retiring or deferring for internal discussion with Nikunj. [17:07]
  • @huzaifaalmesbah recommended keeping issue open and following other teams’ goal structures before proceeding. [18:49]

Tags vs. Categories Discussion

  • @ozgursar raised whether handbook switched from categories to tags; @r1k0 confirmed not yet and questioned necessity. [17:44]
  • @r1k0 identified issue #109 as related tags discussion and committed to reviewing and posting feedback. [21:17]

Announcements and Schedule

  • Weekly patch testing scrub: 2nd and 4th Thursday at 15:00 UTC; weekly test chat: 3rd Thursday; monthly voice chat: 1st Thursday.
  • Multiple calls for testing available including WordPress 7.1, media editor, and responsive styling.

Action items

  • @ikamal create handbook section documenting test flow plugin in moderator guide. [47:06]
  • @ozgursar submit test flow plugin to WordPress directory after handbook documentation complete. [45:08]
  • @Moses Cursor coordinate with AI and performance teams to identify testing content and requirements. [36:02]
  • @r1k0 review issue #109 on tags and post feedback. [21:17]

Files and media

#test-chat-summary

Moses Cursor Ssebunya 2:51 pm on August 6, 2026
Tags: ,   

Team Chat Agenda: 6th August, 2026

Here is the agenda for the upcoming Test Team Voice Chat scheduled for Thursday, 6 August 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

Moses Cursor Ssebunya 3:00 am on August 4, 2026
Tags: , , ,   

Month in Test: August 03, 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 months, 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 (15) 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 (133) 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 (14) 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 🎉

@khushdoms, @jsmansart, @ankitkumarshah, @soyebsalar01, @poojapadamad, @gaurangsondagar, @manhar, @westonruter, @khushi1501

– 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 @sajib1223 @huzaifaalmesbah @nikunj8866 for peer reviewing this post

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

Nikunj Hatkar 3:13 pm on July 30, 2026
Tags: ,   

X-post: Test Team Update: 30 July, 2026

X-post from +make.wordpress.org/updates: Test Team Update: 30 July, 2026

Huzaifa Al Mesbah 5:44 pm on July 22, 2026
Tags: ,   

X-post: Client-Side Media Processing in WordPress 7.1

X-comment from +make.wordpress.org/core: Comment on Client-Side Media Processing in WordPress 7.1

Nikunj Hatkar 6:47 am on July 21, 2026
Tags: ,   

Test Chat Summary: July 16th, 2026

On Thursday, 16 July 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 @andrewssanya @mosescursor (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

  1. Officialize the Test Reports
    • @huzaifaalmesbah suggested this should go through 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, or a Meta TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket should be opened.
    • @nikunj8866 will open a Meta Trac.
  2. Feature and enhancement testing Page
    • @huzaifaalmesbah noted the existing Patch Testing page likely already covers this, and leaned toward improving it rather than creating a new page.
    • @ozgursar referenced the recently updated Call for Testing page as relevant context.
    • Team agreed the existing documentation already covers the proposal.
    • Issue closed by @nikunj8866, with a comment referencing today’s discussion.
  3. Add page with current team goals/initiatives
    • @ozgursar raised whether implementing @sirlouen suggestion would require switching from categories to tags – noting this has come up in prior test chats too.
    • @r1k0 agreed with the tags approach and asked if a current “goals” post already exists – confirmed no.
    • Team agreed to follow @sirlouen suggestion: add a link to the initiatives tag in index.md.
    • Open to anyone – a PR is welcome for this change.

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 6:17 am on July 20, 2026
Tags: ,   

X-post: Help Us Test the New WordPress Playground UI!

X-comment from +make.wordpress.org/playground: Comment on Help Us Test the New WordPress Playground UI!

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 12:14 pm on July 16, 2026
Tags: ,   

X-post: Test Team Update: 16 July, 2026

X-post from +make.wordpress.org/updates: Test Team Update: 16 July, 2026