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