Ringkasan Obrolan Uji Coba: 14 Januari 2026

On Wednesday, 14 January 2026, 02:00 PM UTC, <test-chat> started in  #core-test facilitated by @nikunj8866. The agenda can be found here.

1. Attendance

In attendance was:
@nikunj8866 @fakhriaz @huzaifaalmesbah @sirlouen @shanemuir @harshalkadu @pavanpatil1 @r1k0 @369work @saqib @juanmaguitar @ozgursar @hage (async) @mebo (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

1. Time to Comment Back/Update the Get Set Up for Testing Page.
2. Time to Review/Update the Test Core Tickets with Playground Page.
3. @sirlouen shared 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 be the repository owner. https://github.com/ issue #99 proposing a redesign of the Test Team Updates report.
   • The new format aims to be simpler, focusing on 4 reports across 2 sections (Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and Editor).
   • Only two key data points will be included: Current totals per category The ‘category’ taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. and 2-week changes per category (Closed tickets were considered low value and can be removed.)
   • @nikunj8866 noted the discussion, will review the GitHub thread in detail, and prepare a draft for the next report for team review before publishing.
4. @sirlouen mentioned that the new Test Reports should be officialized after the training program ends, around February.
   • GitHub issue #100 – Officialize the Test Reports was shared as a follow-up.
   • No further action required at this time; the topic will be revisited after the training period.
5. @juanmaguitar introduced an experimental Playground-based tool to simplify the WordPress testing setup(https://github.com/Automattic/experimental-wp-dev-env).

4. Open Floor

• @sirlouen proposed moving the Test Team meetings from bi-weekly to weekly during the training program to increase participation and help trainees get involved in running meetings.
• It was suggested to change the meeting day and time to better align with training sessions, moving away from Wednesdays.
• A new proposed meeting structure was shared:
  Weekly Patch Testing Scrub: Tuesday @ 3:00 PM GMT
  Weekly Test Team Chat: Thursday @ 3:00 PM GMT
  Monthly Recorded Voice Session: First Thursday of each month @ 3:00 PM GMT
• The monthly voice session will be recorded (via Huddle or Zoom) to allow asynchronous participation.
• Patch testing sessions will also run weekly, with @nikunj8866 facilitating the next session, followed by training program members for the coming weeks.
• The proposal has been documented in GitHub issue #103 for feedback and discussion before finalizing.
• Once finalized, the Meetings calendar will be updated accordingly.
• @huzaifaalmesbah asked about supporting Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. diff/patch files in WordPress Playground to make testing easier for contributors.
  • @sirlouen shared that this idea had been discussed earlier with the Playground team, but it does not seem easy to implement.
  • A GitHub PR-based workflow was suggested as a more modern and preferred approach.
  • @sirlouen followed up by raising the question in the #playground 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/. channel to explore possible alternatives, such as using a diff URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org.
• @ozgursar asked whether there is any priority (such as milestones) when querying tickets in Trac.
  • @sirlouen explained that once the reports are officially active, milestoned tickets would naturally take priority.
  • Since the reports are not official yet, contributors are free to pick tickets in any order for now.

5. Announcements

1. WordPress Ecosystem Announcements
2. Test Team Announcements
3. Call for Testing

6. Other Meetings

#core-test