Image Pooja Derashri 12:04 pm on March 12, 2024  

Highlighted Posts

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

Image r1k0 2:51 pm on May 8, 2026
Tags:   

Test Chat Summary: 30th April, 2026

On Thursday, 30 April at 18:00 GMT+3, <test-chat> started in #core-test facilitated by @r1k0. The agenda can be found

1. Attendance

In attendance were: @ozgursar, @mosescursor, @khushdoms, @nikunj8866, @lumiblog, @juanmaguitar, @huzaifaalmesbah, @darshitrajyaguru97, @andrewssanya and @mohkatz (async)

2. Volunteer

This week’s facilitator and note-taker was @r1k0

3. Test Team Discussions

Review and finalize the current handbook PRs before publishing.

The team started its discussion with the first Pull Request by @juanmaguitar on adding a weekly digest workflow for the #core-test.

@r1k0 mentioned he shared his thoughts on the Pull Request and welcomed everyone to test it.

Since the Pull Request needed a bit more work, @juanmaguitar reverted it to a draft till it is properly refined, to begin reviewing and testing.

@r1k0 added that he will include a comment on the Pull Request on how to test the workflow locally and with 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/. He also offered to give anyone an invite to the test Slack and Repo to try out the workflow.

The team moved swiftly to the next agenda item, which was reviewing a Pull Request that seeks to correct a numbering issue in one of the Test Handbook pages.

@ozgursar said he had reviewed the code but noted that it contains HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. tags in the Markdown file. Which needed to be replaced with appropriate Markdown formatting. HTML tags should only be used as a workaround.

@ozgursar asked iamsohilvahora to fix the Pull Request with the suggested changes before the team can approve and merge it.

The team also checked in on the progress of another handbook Pull Request for a new documentation page.

@ozgursar mentioned that the Pull Request only needed a revision of the test report format.

@khushdoms acted fast and made the changes, allowing the team to review before publishing it.

Finally, @r1k0 asked the participants to share any comments or thoughts on a Proposal to update the Test Team meeting schedule.

@mosescursor expressed his excitement for this particular proposal.

@ozgursar encouraged everyone to vote using emojis in the last comment by @nikunj8866: 👍for Tuesday and 👀for Thursday.

@mosescursor reminded everyone that the closing will be closed on Saturday to allow others to cast their votes.

4. Open Floor

@ozgursar asked where the most appropriate place would be to add the 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. in the Handbook, so that other pages can link to it.

He also added that we needed to use the forked version of the plugin in the WPContrib repo.

@r1k0 said we could reference it in the issue and patch reports pages.

Since this is a minor revision, @ozgursar pointed out that new contributors could try working on this.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

Props to @huzaifaalmesbah and @ozgursar for helping review this article and offering feedback

#test-chat-summary

Image Moses Cursor Ssebunya 1:12 pm on May 7, 2026
Tags: , ,   

Test Team Voice Chat Agenda: 7th May, 2026

Here is the agenda for the upcoming Test Team Voice Chat scheduled for Thursday, 7th May, 2026 at 15: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.

#core-test, #gutenberg, #make-wordpress-orgupdates

Image Nikunj Hatkar 12:49 pm on May 5, 2026
Tags: ,   

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

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

Image Moses Cursor Ssebunya 6:00 am on May 5, 2026
Tags: , , ,   

Month in Test: April 5, 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

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 (2) 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 (134) 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 (9) 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 (3) 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 🎉

  • none this Month

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
    • Weekly team meetings are now alternating every Thursday at 15:00 UTC as per schedule
      • Test Team Voice Chat: 1st Thursday of the Month
      • Patch Testing Scrub: 2nd Thursday of the Month
      • Test Team Chat: 3rd Thursday of the Month
      • Patch Testing Scrub – Gutenburg: 4th Thursday of the Month
  3. Call for Testing

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings. Weekly team meetings are now alternating every Thursday at 15:00 UTC as per schedule. Please mark your calendars.

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 helping review this article and offering feedback

#core-test, #full-site-editing, #gutenberg, #make-wordpress-orgupdates

Image r1k0 4:45 am on April 30, 2026
Tags:   

Test Team Chat Agenda: 30th April, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 30 April at 18:00 GMT+3, 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

Image Jonathan Desrosiers 8:54 pm on April 29, 2026
Tags: make.wordpress.org/hosting,   

X-post: Urgent: Testing request to Web hosts for collaborative editing by May 4th

X-comment from +make.wordpress.org/hosting: Comment on Urgent: Testing request to Web hosts for collaborative editing by May 4th

Image Nikunj Hatkar 12:57 pm on April 27, 2026
Tags: , ,   

Test Chat Summary: April 23rd, 2026

On Thursday, 23 April 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 @sajib1223 @khushdoms @juanmaguitar @huzaifaalmesbah @r1k0 @mosescursor @pavanpatil1 @sajjad67 @monzuralam @sumitsingh @mohkatz (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

Review the current handbook PRs before publishing

  1. Add guide for testing Gutenberg tickets with Playground
    • @nikunj8866 reviewed PR and identified missing routes entry in handbook-manifest.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., which is required to properly register the new handbook page.
    • @khushdoms was requested to add the routes entry, with reference to an existing PR.
    • @ozgursar asked whether using ?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/-branch=trunk should be recommended when testing Gutenberg tickets in Playground.
    • @r1k0 raised a concern about including a custom report example instead of using the standard 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. format, potential confusion for new contributors.
  2. Add weekly testing digest workflow for #core-test

Proposed new handbook pages

  1. Proposal: Update Test Team Meeting Schedule for Better Participation
    • This proposal was discussed in the previous meeting.
    • No major objections were raised during this chat.
    • If consensus continues, changes may be applied starting next month.

4. Open Floor

@juanmaguitar opened a new PR to tackle an existing issue #114.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

Props to @mosescursor for peer reviewing this.

#core-test, #test-chat-summary

Image Nikunj Hatkar 8:10 am on April 23, 2026
Tags: ,   

Team Chat Agenda: 23rd April, 2026

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

Image Nikunj Hatkar 12:11 pm on April 21, 2026
Tags: ,   

X-post: Test Team Update: 21 April, 2026

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

Image Nikunj Hatkar 5:01 am on April 21, 2026
Tags: , ,   

Test Chat Summary: April 16th, 2026

On Thursday, 16 April 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:
@ozgursar @nikunj8866 @juanmaguitar @mosescursor @huzaifaalmesbah @r1k0 @khushdoms (async) @mohkatz (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

Review the current handbook PRs before publishing

  1. Add Team Organization page with active and emeritus member sections
    • The team discussed the progress of the handbook PR proposing a new Team Organization page, including sections for Active Members and Emeritus Members.
    • @ozgursar mentioned that maintaining an Active Members list could be difficult and may quickly become outdated. @juanmaguitar agreed with this concern and noted that similar lists in other teams are often hard to maintain.
    • @nikunj8866 suggested defining Active Members based on contributions over the last 2–3 months, including meeting participation, testing, and feedback. He also proposed reviewing the list periodically to keep it accurate.
    • Further discussion led to a preference for focusing on an Emeritus Members list instead. @ozgursar suggested that having only an Emeritus list would be easier to maintain.
    • @nikunj8866 added that past Team Reps could be included in the Emeritus list, recognizing their contributions.
    • The team agreed to continue the discussion in the PR comments to finalize the approach.
  2. Archive old test report pages (testing-instructions, combined-report)
    • The team reviewed the PR aimed at archiving outdated test report pages such as testing instructions and combined reports.
    • @ozgursar noted that the 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. should be referenced, as it was not clearly visible in the updated content. @juanmaguitar clarified that the PR is focused on deprecating old content and keeping only essential references in the handbook, suggesting that additional improvements should be handled in separate issues.
    • @nikunj8866 agreed with this approach and suggested creating a new issue to address the plugin reference. The team agreed that the PR is in good shape and ready for final review and merge after the meeting.
  3. Add cross-links between setup guides and patch testing report page
    • The team discussed a PR focused on improving cross-linking between setup guides and patch testing report pages.
    • @juanmaguitar noted that there are currently no clear instructions or templates for test reports in 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/, only references to patch testing. @nikunj8866 pointed out that there is already an open issue to address this gap and suggested continuing the discussion there.
    • The team agreed that additional issues should be created to define proper guidance for test reports and improve documentation clarity.

Proposed new handbook pages

  1. Create Test (or Test Team) in WordPress GitHub Teams
    • The team discussed a proposal to create a dedicated Test Team group within the WordPress 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/ organization.
    • @juanmaguitar explained that GitHub teams can help organize contributors, making it easier to tag specific groups for testing or triage. @ozgursar compared it to a role-based grouping system.
    • @nikunj8866 raised a question about whether other Make WordPress teams are using similar setups. During the discussion, it was noted that contributors need to be part of the WordPress GitHub organization to be added to such teams.
    • @juanmaguitar created an initial team but was unable to add members due to permission limitations. The team agreed to follow up in the #meta channel to clarify how contributors can be added to the organization.

4. Open Floor

  • @mosescursor questioned whether frequent meetings might be contributing to lower attendance. @juanmaguitar noted that weekly meetings are common across other Make WordPress teams.
  • @nikunj8866 suggested returning to a more focused schedule by alternating meetings:
    • One week for patch testing scrubs
    • One week for Test Team chats
  • @juanmaguitar agreed with this approach, and the team supported the idea. @nikunj8866 created a GitHub issue #154 to continue the discussion and finalize the plan.
  • @nikunj8866 shared a call for volunteers for Table Lead and Co-Lead roles for 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ at 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. Europe 2026. Contributors interested in participating or nominating others were encouraged to apply via the provided form.

5. Announcements

WordPress Ecosystem Announcements

  1. WordPress Core Dev Environment Toolkit: A Faster Path to Your First Core Contribution
  2. Twenty Twenty-Seven: Team Announcement
  3. Defining expectations for Iteration issues
  4. What’s new in Gutenberg 22.9? (8 April)
  5. Elevating Individuals
  6. What’s new for developers? (April 2026)
  7. @wordpress/build, the next generation of WordPress plugin build tooling

Test Team Announcements

Call for Testing

6. Other Meetings

#core-test, #test-chat-summary