Title: Test WordPress Bug Reports
Author: WordPress.org
Published: May 30, 2026

---

# Test WordPress Bug Reports

## In this article

 * [Before you start](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#before-you-start)
 * [Steps](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#steps)
 * [Contribution checklist](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#contribution-checklist)
 * [What happens next](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#what-happens-next)
 * [Help](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#help)

[↑ Back to top](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#wp--skip-link--target)

**Function:** Test
 **Type:** Task **Level:** Beginner

Test bug reports to see if you can trigger the same problem. Many reports turn out
to be pluginPlugin A plugin is a piece of software containing a group of functions
that can be added to a WordPress website. They can extend functionality or add new
features to your WordPress websites. WordPress plugins are written in the PHP programming
language and integrate seamlessly with WordPress. These can be free in the WordPress.
org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. conflicts or user mistakes, not 
WordPress bugs. Your testing helps developers focus on real issues.

## 󠀁[Before you start](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#before-you-start)󠁿

Complete the [common setup](https://make.wordpress.org/handbook/pathways/before-you-begin/)
first, then:

 * **Setup:** Create a [WordPress Trac](https://core.trac.wordpress.org/) account
   to post test reports
 * **Read:** [Issue Reproduction workflow](https://make.wordpress.org/test/handbook/test-reports/issue-reproduction/)
 * **Connect:** Join [#core-test](https://wordpress.slack.com/archives/core-test)
   and introduce yourself

## 󠀁[Steps](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#steps)󠁿

 1. **Find a bug to test.** Browse [WordPress Trac](https://core.trac.wordpress.org/)
    for tickets tagged `needs-testing` or recent bug reports without many comments.
 2. **Read the bug report.** Note the WordPress version, the steps to reproduce, and
    what should happen versus what actually happens.
 3. **Open WordPress Playground.** Go to [playground.wordpress.net](https://playground.wordpress.net/).
    Click the settings icon and set the WordPress version to match the bug report if
    needed.
 4. **Follow the reproduction steps.** Try to trigger the bug exactly as described.
    Test with a default theme (like Twenty Twenty-Four) and no plugins first.
 5. **Post your results.** Comment on the TracTrac Trac is the place where contributors
    create issues for bugs or feature requests much like GitHub.[https://core.trac.wordpress.org/](https://core.trac.wordpress.org/).
    ticket with:

 * Whether you could reproduce the bug
 * WordPress version you tested
 * Browser you used
 * Any variations you tried

## 󠀁[Contribution checklist](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#contribution-checklist)󠁿

 * Bug report selected from Trac
 * Tested in WordPress Playground
 * Results posted on the ticket

## 󠀁[What happens next](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#what-happens-next)󠁿

Developers review test reports to confirm whether bugs are valid. Multiple confirmations
help prioritize fixes. If no one can reproduce an issue, the ticket may be closed
or need more information.

Once comfortable with bug testing, [try testing patches](https://make.wordpress.org/handbook/pathways/test/help-test-patches/)
to validate fixes.

## 󠀁[Help](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#help)󠁿

Stuck? Check the [getting help guide](https://make.wordpress.org/handbook/pathways/before-you-begin/?output_format=md#getting-help),
then ask in [#core-test](https://wordpress.slack.com/archives/core-test).

**Further reading:**
 – [Issue Reproduction workflow](https://make.wordpress.org/test/handbook/test-reports/issue-reproduction/)–
[WordPress Playground documentation](https://wordpress.github.io/wordpress-playground/)

First published

May 30, 2026

May 30, 2026

Edit article

[ Improve it on GitHub: [article_title] ](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fhandbook%2Fpathways%2Ftest%2Ftest-bug-reports%2F&locale=en_US)

Changelog

[ See list of changes: [article_title] ](https://make.wordpress.org/handbook/pathways/test/test-bug-reports/?output_format=md#)

[  Previous: Test for Accessibility](https://make.wordpress.org/handbook/pathways/test/test-for-accessibility/)

[  Next: Audit GatherPress Documentation](https://make.wordpress.org/handbook/pathways/test/audit-gatherpress-documentation/)