Pooja Derashri 12:04 pm on March 12, 2024  

Highlighted Posts

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

Erick Wambua 12:13 am on September 5, 2026
Tags:   

Test Chat Summary: September 3rd, 2026

Huddle Notes: 9/4/26 in #core-test.
AI took notes for this huddle from 1:01:42 AM – 2:25:23 AM GMT+10. The test team reviewed three 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/PRs for the Test handbook, discussed extending the 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. with difficulty ranking and 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/ integration, and explored separating UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. testing from unit testing keywords

Attendees

@mosescursor, @r1k0, @ozgursar, @jns141191, @huzaifaalmesbah, @pbearne, @mohkatz and @khushdoms

Summary

Test Flow Plugin Extension Proposal

@ozgursar noted that Soft Glaze aims to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. tickets by difficulty before sessions, helping moderators select appropriate tasks. [7:51]

@jns141191 raised concern that duplicate tickets spanning years aren’t surfaced, making discovery difficult. [10:18]

@r1k0 identified that the “good first bug” keyword doesn’t necessarily indicate ease of testing, conflating patch difficulty with test difficulty. [11:33]

@r1k0 proposed exporting session history; @pbearne suggested auto-generating posts summarizing completed tickets instead. [17:30]

Slack integration flagged for deferral pending 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 discussion on privacy and security concerns. [19:00]

Pull Requests #186 and #183 Status

PR #186 awaits author updates to address @ozgursar‘s comments before merge. [22:43]

PR #183 has two approvals and @ozgursar‘s support but needs minor rewording before merging. [26:59]

Test Contributor Badge Recognition

@r1k0 fully supports proactively awarding badges to contributors meeting requirements without requests. [30:54]

@pbearne argued that “needs testing” conflates UI testing with unit testing and needs separate keywords for clarity. [33:18]

@r1k0 agreed to discuss keyword separation with the Meta team; @pbearne suggested also exploring E2E/puppet testing tags. [36:28]

Current “need testing” keyword visibility is low; @r1k0 proposed tagging all milestone tickets to increase discoverability. [31:38]

Unit Testing AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) and Coverage

@r1k0 initially meant to ask about Unit testing in the open floor section, but it came up earlier in the session.

@pbearne shared that WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is at 40.47% code coverage; the goal is 80% before retirement. [41:12]

@pbearne noted AI tools simplify test writing; a local Docker setup is required, and writing unit tests is not exclusively reserved for committers. [40:05]

@pbearne offered to mentor anyone interested in writing unit tests and shared a Codecov link for coverage analysis.

@pbearne recommended documentation in the repo README and suggested splitting handbook guidance by skill level (coder vs. UI tester). [45:05]

Announcements and Ecosystem Updates

  • WordPress 7.1 “Mary Lou” released; 7.2 seeking volunteers; 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/ 23.9 and multiple ecosystem updates posted.
  • New WordPress community groups on events.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/ are available for testing and feedback.

Action items

@r1k0 will pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” Soft Glaze to update PR #186 with @ozgursar‘s requested changes. [22:43]

@r1k0 will ping Moses to update PR #183 with suggested rewording. [27:55]

@ozgursar will summarize today’s discussion and ping Soft Glaze for feedback on the test flow proposal. [48:47]

@r1k0 will discuss separating “needs testing” keywords (UI vs. unit vs. E2E) with the Meta team. [36:28]

Files and media

#test-chat-summary

Erick Wambua 1:08 am on September 3, 2026
Tags:   

Test Team Chat Agenda: 03rd September, 2026

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

Huzaifa Al Mesbah 12:59 pm on August 28, 2026
Tags: ,   

X-post: Call for testing: WordPress community groups on events.WordPress.org

X-comment from +make.wordpress.org/meta: Comment on Call for testing: WordPress community groups on events.WordPress.org

Nikunj Hatkar 5:14 am on August 28, 2026
Tags: ,   

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

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

Nikunj Hatkar 12:44 pm on August 24, 2026
Tags: ,   

Test Chat Summary: August 20th, 2026

On Thursday, 20 August 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 @softglaze @ikamal @r1k0 @mosescursor @huzaifaalmesbah @rejaul

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

  1. Test Team Reps: Call for Nominations
    • Nominations for the next Test Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. term are open until 2026-09-12 00:00.
    • To nominate someone (or yourself), comment on the post.
    • Private nominations can be sent to @mosescursor or @nikunj8866 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/.
  2. Revise Test Team Rep duties and qualifications
    • @nikunj8866 has already reviewed the PR and finds it good to merge.
    • Some feedback already exists on the PR; @mosescursor to take a look.
    • Anyone who hasn’t reviewed yet is encouraged to leave feedback directly on the PR.
  3. [Issue Reproduction] Missing guidance on testing unexecutable code paths by forcing conditions
    • Team agreed a common section should be added to the handbook for this scenario.
    • @nikunj8866 proposed a simple addition, as suggested by @huzaifaalmesbah: when a condition can’t be reproduced locally, tag the reporter and add a comment with the needs-test-info keyword.
  4. Proposal: extend TestFlow to help moderators prepare a session, not just run one
    • @ozgursar noted @softglaze found some bugs and will test them as time allows.
    • @ikamal has already commented on the issue.
    • All members encouraged to read the issue and share their thoughts directly in the 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/ thread.
  5. Recognize WordPress 7.1 Test Contributors – Badge Awards & Blog Post
    • Following the same approach used for 7.0, the team will recognize WordPress 7.1 test contributors via badges and a blog post.
    • @huzaifaalmesbah to prepare the contributor docs, following the same process as last time.
    • Once the docs are ready, @mosescursor will review and assign badges to eligible contributors.

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 2:27 pm on August 20, 2026
Tags: ,   

Team Chat Agenda: 20th August, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 20 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 2:00 pm on August 20, 2026
Tags:   

Test Team Reps: Call for Nominations

It’s time again to nominate the Test Team Reps who will serve for the next 12 months!

This Call for Nominations is open until 2026-09-12 00:00. Please leave a comment identifying your nominee(s) before then.

For a quick refresher of Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. roles across the project, please see the Team Reps post on Team Updates.

The Role

Reps in the Test Team perform primary and secondary (or backup) duties to help support team chats, make updates to the team’s blog and handbook, remove blockers, keep a pulse on team objectives, and promote testing opportunities within the WordPress project.

As a reminder, Reps are not called “team leads” for a reason. While people elected as Team Reps will generally come from the pool of folks that people think of as experienced leaders, the Team Rep role is designed to change hands regularly.

Test Team Rep duties include:

  • Write bi-weekly Test Team Update posts, and post to Team Updates page.
  • Write Monthly Month in Test posts, and post to Make WordPress Test.
  • Write agenda for bi-weekly <test-chat> sessions (example).
  • Run alternating weekly <test-chat> (example) and <Patch Testing> (example) sessions in #core-test.
  • Write <test-chat> session recaps, and post to Make WordPress Test.
  • Run Voice Chat sessions in #core-test every 1st Thursday of every month.
  • Help new contributors with their WordPress Testing related queries.
  • Help raise awareness for testing needs, especially for upcoming releases.
  • Raise issues or red flags that other teams should be aware of or discussing.

These duties are shared between the two Reps (see Rep Responsibilities on the Team Rep page).

Qualifications

Candidates for the Test Team Rep position should be active, reliable, and trusted team members who understand WordPress testing and are willing to represent, support, and grow the team to better serve the WordPress 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. project.

Test Team Reps serve a one-year term and should commit approximately 2–4 hours per week. To be eligible, nominees must have been active in the Test Team within the previous 12 months by completing one or a combination of:

  • Leading at least 3 Test Team chats, including published recaps.
  • Managing at least 6 Patch Testing Scrubs.

A combination may also qualify; for example, Leading 2 Test Team chats and managing 2 Patch Testing Scrubs would also qualify as an active member.

These eligibility requirements apply to contributions made within the 12 months prior to the nomination period. Not all Test Team Reps have to be technical experts, but they should have a good understanding of the testing processes and be able to communicate effectively with both technical and non-technical team members. For not tech savvy members, being able to lead Test Team chats is a good way to demonstrate communication skills, while for technical members, managing Patch Testing Scrubs is a good way to demonstrate technical expertise.

How Test Team Elections Work

Step 1: Call for Nominations 📣

The first step is to reach out to the community with a Call for Nominations (this post!)

Please nominate in the comments of this post. You can write a comment as simple as “I nominate @the_persons_username.” Self-nominations are also welcome by leaving a comment such as “I nominate myself.”

Private nominations can be submitted by contacting @mosescursor or @nikunj8866 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/.

If you’ve been nominated, please accept or decline the nomination as a reply to the same comment.

⏰ The deadline for nominations is 2026-09-12 00:00

After the deadline, each nominee will be contacted to discuss qualifications and to confirm their acceptance of the nomination.

If you get nominated, please do not feel like you have to say “yes”. It’s okay for you to decline the nomination if you don’t feel like this is the right fit for any reason. “Thank you, but no thank you!” 😉

Step 2: Vote for Team Reps 🗳

An election will happen only if there are more than two accepted nominations within the nomination period; otherwise the nominees will become the new Test Team Reps.

If held, the election will be conducted by an anonymous poll. The poll will remain open for 2 weeks.

Step 3: Announce Team Reps 🎉

Once uncontested nominations have been accepted, or in the event of an election the voting period has passed, the new Test Team Reps will be announced in a post (example).

Time to Nominate!

Are you ready? It’s time to nominate folks to serve as our Test Team Reps for the new term! If you have any questions, please feel free to ask in the comments.

Props to @nikunj8866 @oglekler @sirlouen for pre publish review of this post.

#team-reps

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