WordPress 7.0 is here, and it wouldn’t have been possible without the incredible effort of the testing community. Behind every stable release is a dedicated group of people who download beta versions, apply patches, reproduce bugs, and report what they find. They are the safety net that catches issues before they reach millions of WordPress users.
This post is a celebration of those people.
7.0 Testing, By the Numbers
These numbers were compiled using the WordPress Test Contribution Tracker, an automated tool that scans Trac tickets, classifies test contributions, and identifies new contributors. If we missed your contribution or a number looks off, let us know in the comments – we’ll gladly fix it.
During the WordPress 7.0 release cycle, the testing community achieved something remarkable:
– 427 Core Trac tickets were tested
– 132 unique contributors participated in testing and bug reproduction
– 89 of them were new contributors — testing WordPress for the very first time and without a Test Contributor badge yet
– 113 contributors tested patches directly
– 34 contributors helped reproduce confirmed bugs
– 25+ countries across 6 continents were represented
That’s 67% of all test contributors being completely new to WordPress testing. If that’s not a sign of a growing and healthy community, we don’t know what is.
A Global Effort
Testing WordPress is truly a worldwide effort. During the 7.0 cycle, contributors joined in from 25+ countries across 6 continents, working across time zones and languages to make WordPress better for everyone.
🇮🇳 India led the way with 47 contributors — more than a third of all testers. 🇧🇩 Bangladesh followed with 15 contributors, and 🇺🇸 United States contributed 11. Rounding out the top countries: 🇩🇪 Germany (4), 🇫🇷 France (3), 🇪🇸 Spain (3), 🇵🇭 Philippines (3), 🇯🇵 Japan (2), 🇦🇺 Australia (2), and 🇺🇬 Uganda (2).
Contributors also joined from 🇰🇪 Kenya, 🇵🇰 Pakistan, 🇧🇹 Bhutan, 🇩🇿 Algeria, 🇳🇱 Netherlands, 🇦🇹 Austria, 🇹🇳 Tunisia, 🇪🇬 Egypt, 🇻🇳 Vietnam, 🇵🇹 Portugal, 🇳🇵 Nepal, 🇮🇹 Italy, 🇸🇪 Sweden, and 🇨🇭 Switzerland — each with 1 contributor proving that even a single test makes a difference.
Every Contribution Counts
We want to recognize every single person who tested a ticket, left a “reproduced” comment, or tried a patch during the 7.0 cycle. Whether you tested 36 tickets or just 1, you made a difference.
Here’s the full list of all 132 contributors who participated in testing or reproduction for WordPress 7.0:
@369work @abcd95 @abdullah17 @abduremon @adnanhyder @agnieszkaszuba @alh0319 @alexodiy @amesplant @amin7 @andrewssanya @ankitkumarshah @arkaprabhachowdhury @audrasjb @benniledl @berislav.grgicak @chexee @darshitrajyaguru97 @dhruvang21 @dhrumilk @dilip2615 @dlh @dmsnell @donmhico @drysand @ekla @ellatrix @emptyopssphere @fabiankaegy @fakhriaz @gaisma22 @gaurangsondagar @gauri87 @gautammkgarg @gulamdastgir04 @hbhalodia @hmbashar @huzaifaalmesbah @iamadisingh @ibrahimriaz @im3dabasia1 @immeet94 @jabir20 @jadavsanjay @jarodortegaaraya @jigarkahar @joedolson @jonsurrell @joppuyo @josephscott @jsmansart @juanfra @kelvinballoo @khokansardar @khushi1501 @khushdoms @lakshyajeet @louischan @mabfahad @madhavishah01 @mai21 @manhar @manhphucofficial @manishxdp @maulikmakwana2008 @maxschmeling @mcsf @mdibrahimk48 @mindctrl @mirmpro @mokshasharmila13 @monzuralam @mosescursor @navi161 @nilambar @nimeshatxecurify @niravsherasiya7707 @noruzzaman @ocean90 @olmostblue @opurockey @ozgursar @palak678 @pavanpatil1 @pbiron @peterwilsoncc @phpbits @pmbaldha @poena @pooja1210 @poojapadamad @pratiklondhe @pratiknawkar94 @r1k0 @rahultank @ramonopoly @ravichudasama01 @rcorrales @rinkalpagdar @rishavdutta @rollybueno @ronya4927 @sabernhardt @sainathpoojary @sajib1223 @sajjad67 @sandeepdahiya @shailu25 @shekharnwagh @shibleemehdi @showravhasan @siliconforks @SirLouen @soyebsalar01 @sourabhjain @spiraltee @sukhendu2002 @suhan2411 @swissspidy @tobiasbg @tusharaddweb @tusharbharti @ugyensupport @valentingrenier @vgnavada @westonruter @wildworks @xwolf @youknowriad @yusufmudagal
Thank you, all of you. WordPress 7.0 is better because of your time and effort.
Get Involved — Help Test WordPress 7.1
The WordPress 7.1 cycle is already underway, and we’d love for you to join the testing effort. Testing is one of the most impactful ways to contribute to WordPress — and you don’t need to be a developer. If you can install WordPress, follow instructions, and describe what you see, you can be a test contributor.
Here’s how to get started:
1. Choose Your Setup
The quickest way is Test Core Tickets with Playground — test directly in your browser with zero setup. For applying .patch/.diff files or running test suites, follow the Set Up a Testing Environment guide to get a local Docker-based install running. To test the block editor, see the Test Gutenberg guide.
2. Find Something to Test
There are tickets and PRs waiting for testers right now:
– Core Trac — Needs Testing — All open Core tickets needing testing, across all milestones
– Gutenberg Issues — Needs Testing — Open Gutenberg issues that need reproduction or verification
– Gutenberg PRs — Needs Testing — Pull requests that need someone to verify the fix works
You can also check the Calls for Testing on the Test Team blog — these are focused, guided testing tasks with step-by-step instructions, perfect for new contributors.
3. Test and Report
Once you’ve found a ticket, there are two main types of testing you can do:
– Issue Reproduction: Confirm that a reported bug is real by following the steps and describing your results. Use the Issue Reproduction template from the handbook.
– Patch Testing: Apply a patch and verify it fixes the issue (or delivers the expected feature). Watch for regressions where the patch fixes one thing but breaks another. Use the Patch Testing template from the handbook.
Both templates include fields for your environment (OS, PHP version, WordPress version, browser) and space for your results. Just copy, fill in, and post as a comment on the ticket.
4. Help with Triage
If you’re comfortable navigating Trac, you can also help with ticket triage. When a ticket is tagged needs-testing, testers evaluate it and decide the next step. The Trac Keyword Triage Guide explains the four keywords testers manage (needs-testing, needs-test-info, dev-feedback, needs-refresh) and includes ready-to-use comment templates.
5. Get Recognized
Contributors who provide meaningful test contributions – reproduction reports, patch tests, unit tests, or documentation updates – earn the Test Contributor badge on their WordPress.org profile.
Learn more at Test Team Profile Badges.
Join the Community
– #core-test on Slack — The main hub for testing discussions, questions, and coordination
– Test Team Handbook — Everything you need to know about testing WordPress
– Contributor Day — Join a Contributor Day at a WordCamp near you, or participate remotely
Let’s keep making WordPress better, one test at a time. 🎉
Props to @ozgursar, @nikunj8866, @mosescursor for helping review this article and offering feedback.