Source: Make WordPress: Test

At a high level there are four parts to facilitating a call for testing within the WordPress project: Determine what needs testing. Write and share the call for testing. Respond to feedback/close the feedback loop. Summarize the results. The final two steps are sometimes optional, depending on how the call for testing is approached and…

Triage Tags Triage of posts on make/flow is done with tags. Component Tag make/flow posts with the relevant core component, iOS component, or Android component. The component is the most important triage tag. When tagging a visual record that crosses components, tag all exercised components. Tagging by component allows component teams to follow the make/flow…

This page offers comprehensive information about Test Team Profile Badges and the process for requesting these badges for your WordPress.org profile. Test Contributor Badge To earn a Test Contributor Badge, you must have completed at least any the following: Submitted five test reports for tickets, comprising an issue reproduction, and/or patch testing. Acceptable reports should…

For more information about the role Test Team members play in the WordPress project, see the Test Team Handbook Homepage. Prepare for Contributor Day In order to make the most of your time meeting and working with fellow contributors, follow these helpful pre-Contributor Day tips! Did you know? Your WordPress.org profile displays your WordPress.org, Slack,…

Many tickets receive patches before test reviewers have had a chance to list test steps or perform reproduction testing. If this is the case, it is helpful to begin by outlining the test instructions and expected results, followed by the actual reproduction and patch validations. Alternatively, testers can post testing instructions first (if not supplied), followed by…

In context of bug repositories such as Trac or GitHub, triage means sorting, labeling, and closing duplicate incoming issues and testing means manually testing bug reports, questions, and feature requests. Trac Triage When working with WordPress Core Trac, testers use a specific set of keywords to signal the state of a ticket. For a full…

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, multisite with subdomains, etc). Delete any sections from the report that are not applicable. Example reproduction reports:…

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 Core Tickets with Playground Go to the…