Title: Combined Report
Author: WordPress.org
Published: October 30, 2025
Last modified: April 21, 2026

---

# Combined Report

## In this article

 * [Bug/Defect Combined Report Template](https://make.wordpress.org/test/handbook/archive/archived-test-reports/combined-report/?output_format=md#bug-defect-combined-report-template)
 * [Feature or Enhancement Combined Report Template](https://make.wordpress.org/test/handbook/archive/archived-test-reports/combined-report/?output_format=md#feature-or-enhancement-combined-report-template)

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

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 a reproduction report, and then a patch test report, each in separate comments.

## 󠀁[Bug/Defect Combined Report Template](https://make.wordpress.org/test/handbook/archive/archived-test-reports/combined-report/?output_format=md#bug-defect-combined-report-template)󠁿

An example combined report might look like this (some sections removed for brevity):

    ```
    == Test Report

    Patch tested: REPLACE_WITH_PATCH_URL

    === Steps to Reproduce or Test
    1. First step.
    2. Second step.
    3. 🐞 Bug occurs.

    === Expected Results
    When testing a patch to validate it works as expected:
    - ✅ What should happen when running the test

    When reproducing a bug:
    - ❌ Error condition occurs.

    === Environment
    - OS: Operating System X.Y.Z
    - Web Server: Server Name X.Y.Z
    - PHP: X.Y.Z
    - WordPress: X.Y-Z
    - Browser: Browser Name X.Y.Z
    - Theme: Theme Name X.Y.Z 
    - Active Plugins:
      - Plugin 1 X.Y.Z
      - Plugin 2 X.Y.Z

    ==== Actual Results
    When reproducing a bug/defect:
    - ❌ Error condition occurs.

    When testing the bugfix patch:
    - ✅ Issue resolved with patch.
    ```

## 󠀁[Feature or Enhancement Combined Report Template](https://make.wordpress.org/test/handbook/archive/archived-test-reports/combined-report/?output_format=md#feature-or-enhancement-combined-report-template)󠁿

An example combined report might look like this (some sections removed for brevity):

    ```
    == Test Report

    Patch tested: REPLACE_WITH_PATCH_URL

    === Steps to Test
    1. First step.
    2. Second step.
    3. Third step.
    ...
    N. Last step.

    === Expected Results
    Lists each expected result or behavior, i.e. what should happen when running the test(s):
    - ✅ Expected result #1
    - ✅ Expected result #2

    === Environment
    - OS: Operating System X.Y.Z
    - Web Server: Server Name X.Y.Z
    - PHP: X.Y.Z
    - WordPress: X.Y-Z
    - Browser: Browser Name X.Y.Z
    - Theme: Theme Name X.Y.Z 
    - Active Plugins:
      - Plugin 1 X.Y.Z
      - Plugin 2 X.Y.Z

    === Actual Results
    - ✅ Expected result #1 works as expected with patch.
    - ✅ Expected result #2 works as expected with patch.
    ```

First published

October 30, 2025

Last updated

April 21, 2026

Edit article

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

Changelog

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

[  Previous: Testing Instructions](https://make.wordpress.org/test/handbook/archive/archived-test-reports/testing-instructions/)