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 GitHub 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 flow 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. plugin 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 Slack 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 UI 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 filter 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 Meta 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 Accessibility 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 core 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; Gutenberg 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.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 ping 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
