Title: Test Chat Summary: 12th February, 2026
Author: Huzaifa Al Mesbah
Published: February 14, 2026
Last modified: February 16, 2026

---

 [  ](https://profiles.wordpress.org/huzaifaalmesbah/) [Huzaifa Al Mesbah](https://profiles.wordpress.org/huzaifaalmesbah/)
5:11 pm _on_ February 14, 2026     
Tags: [core-test ( 234 )](https://make.wordpress.org/test/tag/core-test/),
[test-chat-summary ( 17 )](https://make.wordpress.org/test/tag/test-chat-summary/)

# Test Chat Summary: 12th February, 2026

On [ Thursday, 12th February 2026 at 15:00 GMT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260212T1500),`
<test-chat>` started in [#core-test](https://wordpress.slack.com/archives/C03B0H5J0/p1768899660126299)
facilitated by [@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/).
The agenda can be found [here](https://make.wordpress.org/test/2026/02/12/test-team-chat-agenda-12th-february-2026/).

## 1. **Attendance**

In attendance was: [@ozgursar](https://profiles.wordpress.org/ozgursar/) [@mehrazmorshed](https://profiles.wordpress.org/mehrazmorshed/)
[@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/) [@r1k0](https://profiles.wordpress.org/r1k0/)
[@andrewssanya](https://profiles.wordpress.org/andrewssanya/) [@mohkatz](https://profiles.wordpress.org/mohkatz/)
[@noruzzaman](https://profiles.wordpress.org/noruzzaman/) [@nikunj8866](https://profiles.wordpress.org/nikunj8866/)(
async)

## 2. Volunteer

This week’s facilitator was [@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/)

This week’s Note-taker was [@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/)

## 3. Test Team Discussions

**Daily / Bi-Daily Testing Workflow Notice Proposal**

[@sajib1223](https://profiles.wordpress.org/sajib1223/) proposed adding a daily 
or bi-daily workflow notice to highlight tickets that need testing, include a quick-
start guide, and possibly share weekly testing stats. The goal is to keep testing
active, attract new contributors, and remind existing contributors.

[@ozgursar](https://profiles.wordpress.org/ozgursar/) asked how this would be automated.
[@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/) suggested implementing
it similar to the 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/](https://wordpress.org/gutenberg/)“
Needs Testing” announcer and later mentioned that he liked the idea and found it
helpful.

[@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/) also suggested
that **[@sajib1223](https://profiles.wordpress.org/sajib1223/)** create 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/](https://github.com/)
issue in the Test Handbook repository so the broader Test Team can discuss and provide
feedback.

[@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/) proposed manually 
highlighting TRACTrac Trac is the place where contributors create issues for bugs
or feature requests much like GitHub.[https://core.trac.wordpress.org/](https://core.trac.wordpress.org/).
tickets with the **needs-testing** keyword, especially non-bug tickets in the 7.0
milestone that should be prioritized before the upcoming BetaBeta A pre-release 
of software that is given out to a large group of users to trial under real conditions.
Beta versions have gone through alpha testing in-house and are generally fairly 
close in look, feel and function to the final product; however, design changes often
occur as part of the process. 1 release.

**Sync Weekly Meetings Section with the New CoreCore Core is the set of software
required to run WordPress. The Core Development Team builds WordPress. Test Meeting
Structure**

The team discussed updating the Weekly Meetings section to align with the new Core
Test meeting structure. [@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/)
asked [@mosescursor](https://profiles.wordpress.org/mosescursor/) and [@nikunj8866](https://profiles.wordpress.org/nikunj8866/)
to review the issue. [@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/)
offered to handle the update, mentioning that it only required editing page content.

[@nikunj8866](https://profiles.wordpress.org/nikunj8866/) confirmed that if JuanMa
had the necessary access, he could proceed with updating the page. The update was
completed by [@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/)

**Proposal – Restructure Test Handbook to Support Multiple Testing Domains**

The team discussed the proposed project-based directory structure for the Test Handbook
and next steps for implementation. Feedback was requested to help move the proposal
forward.

[@ozgursar](https://profiles.wordpress.org/ozgursar/) shared that the new directory
structure looks good and mentioned submitting a PR to add email testing instructions,
which could fit into the new structure.

[@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/) recommended avoiding
duplicated information and instead linking to resources in other handbooks where
possible.

[@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/) suggested first
restructuring the Testing section under _get-setup-for-testing_, then placing email
testing instructions in the most appropriate location.

The team agreed to continue the detailed discussion and feedback in the [related GitHub issue](https://github.com/WordPress/test-handbook/issues/111)
before finalizing the structure and proceeding with updates.

## 4. Open Floor

During the Open Floor, [@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/)
highlighted a major feature planned for WordPress 7.0 [the proposal to merge the WP AI Client into WordPress 7.0](https://make.wordpress.org/core/2026/02/03/proposal-for-merging-wp-ai-client-into-wordpress-7-0/).
He shared the related [Trac ticket ](https://core.trac.wordpress.org/ticket/64591)
and noted that the post includes a “Call for Feedback and Testing,” encouraging 
contributors to review and provide feedback. He also reminded the team about the
upcoming [WP 7.0 Bug Scrub](https://make.wordpress.org/core/2026/01/27/bug-scrub-schedule-for-wordpress-7-0/)
happening shortly after the meeting.

[@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/) thanked [@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/)
for surfacing the feature and asked about the [WP Trac Triager Chrome extension](https://chromewebstore.google.com/detail/wp-trac-triager/fhlhkchpljijkhhmichmfdhedangngol)
created by [@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/) — how it
works and how it can support the Test Team.

[@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/) explained that the
extension enhances Trac ticket triage by surfacing key information in a clearer 
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., including:

 * The latest comments
 * Milestone history
 * Keyword explanations
 * Component maintainers
 * Keyword change history
 * Quick links to comments

He shared that the tool is available on the [Chrome Web Store](https://chromewebstore.google.com/detail/wp-trac-triager/fhlhkchpljijkhhmichmfdhedangngol)
and open to feedback via [GitHub](https://github.com/juanma-wp/wp-trac-triager).

[@ozgursar](https://profiles.wordpress.org/ozgursar/) noted that the extension significantly
improves Trac ticket triaging, especially for tickets with long discussion histories.

[@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/) added that the
tool helps with quick navigation and makes it easier to identify reporters, committers,
and maintainers at a glance. He expressed appreciation for the tool, highlighting
that it helps the Test Team work more efficiently.

## 5. Announcements

### **WordPress Ecosystem Announcements**

 * [Piloting the AI Leaders Micro-Credential](https://wordpress.org/news/2026/02/ai-leaders-credential/)
 * [AI Guidelines for WordPress](https://make.wordpress.org/ai/2026/02/01/ai-guidelines-for-wordpress/)
 * [Proposal for merging WP AI Client into WordPress 7.0](https://make.wordpress.org/core/2026/02/03/proposal-for-merging-wp-ai-client-into-wordpress-7-0/)
 * [What’s new in Gutenberg 22.5? (04 February)](https://make.wordpress.org/core/2026/02/04/whats-new-in-gutenberg-22-5-04-february/)
 * [WordPress 6.9.1 is now available](http://WordPress%206.9.1%20is%20now%20available)
 * [Bug Scrub Schedule for WordPress 7.0](https://make.wordpress.org/core/2026/01/27/bug-scrub-schedule-for-wordpress-7-0/)
 * [What’s new for developers? (February 2026)](https://developer.wordpress.org/news/2026/02/whats-new-for-developers-february-2026/)

### **Test Team Announcements**

 * [Month in Test: February 8, 2026](https://make.wordpress.org/test/2026/02/09/month-in-test-february-8-2026/)
 * [Test Chat Moderator Guide published in the handbook](https://make.wordpress.org/test/handbook/team-reps/test-chat-moderator-guide/)
 * [Test Team Program Recap](https://make.wordpress.org/test/2026/02/05/the-test-team-training-program-recap/)
 * [Test Chat Summary: 5th February 2026](https://make.wordpress.org/test/2026/02/06/test-chat-summary-5th-february-2026/)

### **Call for Testing**

 * [Call for Testing: Exploring New AI Experiments](https://make.wordpress.org/ai/2026/02/04/call-for-testing-exploring-new-ai-experiments/)
 * [Call for Testing – Customizable Navigation (“Mobile”) Overlays](https://make.wordpress.org/test/2026/01/27/call-for-testing-customizable-navigation-mobile-overlays/)
 * We have [Patch Testing issues for the WordPress 7.0 ](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~has-patch+needs-testing&milestone=7.0&col=id&col=summary&col=status&col=keywords&col=owner&col=type&col=priority&col=component&col=changetime&desc=1&order=changetime)
   milestone that need testing.
 * We have [Patch Testing issues Awaiting Review](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~needs-testing+has-patch&milestone=!Awaiting+Review&milestone=!&col=id&col=summary&col=status&col=milestone&col=keywords&col=type&col=priority&col=component&col=changetime&desc=1&order=changetime)
   that need testing.

## 6. Other Meetings

 * [Tuesday, 17 February 2026 at 15:00 GMT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260217T1500)–`
   <patch-testing-session>` in [#core-test](https://wordpress.slack.com/messages/core-test/)
 * [Thursday, 19 February 2026 at 15:00 GMT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260219T1500)–`
   <test-chat>` in [#core-test](https://wordpress.slack.com/messages/core-test/)

_Props to [@bosskhj](https://profiles.wordpress.org/bosskhj/) for reviewing this
post_

[#core-test](https://make.wordpress.org/test/tag/core-test/), [#test-chat-summary](https://make.wordpress.org/test/tag/test-chat-summary/)

### Share this:

 * [  Threads ](https://make.wordpress.org/test/2026/02/14/test-chat-summary-12th-february-2026/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/test/2026/02/14/test-chat-summary-12th-february-2026/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/test/2026/02/14/test-chat-summary-12th-february-2026/?share=bluesky)
 * [  X ](https://make.wordpress.org/test/2026/02/14/test-chat-summary-12th-february-2026/?share=x)
 * [  Facebook ](https://make.wordpress.org/test/2026/02/14/test-chat-summary-12th-february-2026/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/test/2026/02/14/test-chat-summary-12th-february-2026/?share=linkedin)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2026%2F02%2F14%2Ftest-chat-summary-12th-february-2026%2F%23respond&locale=en_US)

### Like this:

Like Loading…

### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/test/2026/02/14/test-chat-summary-12th-february-2026/?output_format=md#respond)󠁿

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2026%2F02%2F14%2Ftest-chat-summary-12th-february-2026%2F&locale=en_US)
to post a comment.

# Post navigation

[← Test Team Chat Agenda: 12th February, 2026](https://make.wordpress.org/test/2026/02/12/test-team-chat-agenda-12th-february-2026/)

[Test Scrub Schedule for WordPress 7.0 →](https://make.wordpress.org/test/2026/02/17/test-scrub-schedule-for-wordpress-7-0/)