The Test Team helps manage testing and triage across the WordPress ecosystem. They focus on user testing of the editing experience and WordPress dashboard, replicating and documenting bug reports, and supporting a culture of review and triage across the project.
Welcome to the Test Team Handbook! In these pages you can learn how and where to get involved in testing WordPress. If you want to help improve WordPress quality and usability, and advance the development process, then you’ve come to the right place!
While the Test Team originally stemmed from the Core Team, contributions to WordPress testing have grown to encompass the entire WordPress ecosystem. Of course the efforts of Test Team contributors benefit WordPress and the core editor, but also sub-projects like Design and Themes, Accessibility, mobile apps, WP-CLI, Feature Projects, importers, and even WordPress.org itself.
Test Team contributions touch on all aspects of manual and automated testing within the project, including:
- WordPress release beta testing and editor pre-release testing
- full site editing (FSE) outreach
- issue reproduction and patch testing
- feature and enhancement testing
- end-to-end (E2E) testing
- issue triage and bug scrubs
- education, outreach, and documentation
With such a wide range of opportunities available, contributors are sure to find an area of interest to help make WordPress better.
Contributors to testing have a wide variety of experience and technical knowledge, from beginners with little WordPress experience to seasoned developers who have contributed for years.
Just as WordPress is open to anyone and everyone, numerous opportunities exist for Test Team contributions regardless of individual skill level. And, like the larger WordPress community, contributors in the Test Team are enthusiastic to share their knowledge and expertise.
Ready to get started? Here are some links to get you on your way:
- Join the #fse-outreach-program — the fastest way to get testing
- Guidelines for writing great Test Reports
- Tickets needing issue reproduction (created in the last week)
- Tickets needing patch testing (modified in the last week)
- Tickets needing unit tests (modified in the last month)
- Editor issues needing testing
- Editor issues with automated testing requirements (e.g. unit or E2E tests)