💡If you don’t know how to start, join the Patch testing scrub ☕ on Thursday at 4:00 pm UTC in the #core-test.

Test Ticket Queue 

“(change: N)” represents changes from prior 2 weeks (unless noted).
Note that review implies code validation and addresses developers.

Current totals (since December 8, 2025):

• Need testing info: 48 (change: 0)
• Need to reproduce issue: 170 (change: -1)
• Need patch testing: 25 (change: 0)
• Need unit tests: 97 (change: -1)
• Need review (have patch and unit tests): 276 (change: +6)

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/

• Needs More Info: 10 (change: +9)
• Needs Testing: 0 (change: -14)

 New/Changed two weeks:

• Need testing info: 1 (change: +1)
• Need to reproduce issue: 1 (change: +1)
• Need patch testing: 4 (change: +2)
• Need unit tests: 1 (change: -1)
• Need review (have patch and unit tests): 15 (change: -6)

Closed two weeks (after testing):

Closing tickets that are reporting personal issues or duplicates early saves time of contributors to do something productive.

• Need testing info: 2 (change: +2)
• Need to reproduce issue: 8 (change: -7)
• Need patch testing: 0 (change: 0)
• Need unit tests: 0 (change: 0)
• Need review (have patch and unit tests): 0 (change: -1)

To know more about these reports and what you can do, connect with the Test Team over in #core-test or check the full meetings schedule.

+make.wordpress.org/test/

#test

Note: We have updated the 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. criteria for identifying reproduction issues. As a result, the ticket counts in this report may differ significantly from previous bi-weekly reports. These numbers reflect the new filtering logic and will be used going forward.

💡If you don’t know how to start, join the Patch testing scrub ☕ on Thursday at 4:00 pm UTC in the #core-test.

Test Ticket Queue 

“(change: N)” represents changes from prior 2 weeks (unless noted).
Note that review implies code validation and addresses developers.

Current totals (since November 24, 2025):

• Need testing info: 48 (change: 0)
• Need to reproduce issue: 171 (change: 0)
• Need patch testing: 25 (change: -1)
• Need unit tests: 98 (change: +2)
• Need review (have patch and unit tests): 270 (change: +7)

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/

• Needs More Info: 1 (change: -4)
• Needs Testing: 14 (change: -5)

 New/Changed two weeks:

• Need testing info: 0 (change: -1)
• Need to reproduce issue: 0 (change: 0)
• Need patch testing: 2 (change: -1)
• Need unit tests: 2 (change: -1)
• Need review (have patch and unit tests): 21 (change: +11)

Closed two weeks (after testing):

Closing tickets that are reporting personal issues or duplicates early saves time of contributors to do something productive.

• Need testing info: 0 (change: 0)
• Need to reproduce issue: 15 (change: +10)
• Need patch testing: 0 (change: 0)
• Need unit tests: 0 (change: 0)
• Need review (have patch and unit tests): 1 (change: +1)

To know more about these reports and what you can do, connect with the Test Team over in #core-test or check the full meetings schedule.

+make.wordpress.org/test/

#test