Content type: Handbook

In context of bug repositories such as TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. or 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…

Issue reproduction is a critical step in communicating and confirming how to trigger the undesired behavior that was reported in the ticket. Provide as much of the environment information as possible and any special configuration considerations (using Docker, multisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a…

Once a patch is made available for a ticket, it is critical to validate that the code change (a) addresses the issue (for bug report) or (b) delivers the expected behavior or result (for feature or enhancement). If you haven’t applied a patch yet, see Test Core Tickets with Playground or Test Core Tickets with…

What Is a Test Report? A test report provides a documented record of a reported issue. It answers questions such as: Does the issue occur for other users? Under what conditions does the issue occur? How can the issue be detected? What are the impacts of the issue? How does the issue appear to users?…

WordPress Playground is an online platform that lets you experiment and learn about WordPress without affecting your live website. It’s a virtual sandbox where you can test features, designs, and settings in a safe and controlled environment. More about WordPress Playground can be read here. How to Test CoreCore Core is the set of software…

Testing Instructions provide a list of steps for testers to follow in reproducing a reported issue (before a patch) and/or validating the expected behavior or result actually happens (after applying a patch). Adding these instructions within the ticket provides needed testing information without testers having to duplicate the same information over and over in test…

Getting involved with WordPress testing is a great way to contribute and also a chance to learn. Trying to reproduce bugs and testing patches exposes you to real bugs, edge cases, and development decisions that sharpen your skills and deepen your understanding of how WordPress is built. And regardless of your experience level or how…

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! Duty of Care While the Test Team originally stemmed from the Core…

For a quick refresher of Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. roles across the project, please see the Official Team Reps post on Team Updates. Current Reps…

This section contains all the archive content from the Test Handbook, these are those pages that were useful in the past because of certain ongoing activities and we think that might be useful in the future if those activities are resumed. Full Site Editing Outreach Program: link GutenbergGutenberg The Gutenberg project is the new Editor…