It's time to get hands on the review of the new Reports
Here I'm going to propose two alternatives, for Reproduction and Patch Testing.
== Reproduction Report
=== Environment
- WordPress:
- PHP:
- Server:
- Database:
- Browser:
- OS:
- Theme:
- MU Plugins:
- Plugins:
=== Steps taken
1.
2.
x. 🐞 Bug occurs / ❌ Bug is not occurring
=== Expected behavior
- Explain what behaviour you were expecting from the ticket information
=== Additional Notes
- Any additional details worth mentioning.
=== Screenshots/Screencast with results
- Screenshot showcasing the problem or the bug not ocurring.
=== Support Content
- Here you can add any support content useful for testing
For example:
1. Blueprint JSON
2. Website Playground URL with parameters
3. Snippets of code
4. Additional Screenshots
5. etc...
== Patch Testing Report
Patch Tested: Link to the diff patch or GitHub Pull Request
=== Environment
- WordPress:
- PHP:
- Server:
- Database:
- Browser:
- OS:
- Theme:
- MU Plugins:
- Plugins:
=== Steps taken
1.
2.
x. ✅ Patch is solving the problem / ❌ Patch is failing
=== Expected result
- Explain what results you were expecting from this patch.
=== Additional Notes
- Any additional details worth mentioning.
=== Screenshots/Screencast with results
- Screenshot/Screencast before
- Screenshot/Screencast after
=== Support Content
- Here you can add any support content useful for testing
For example:
1. Blueprint JSON
2. Website Playground URL with parameters
3. Snippets of code
4. Additional Screenshots
5. etc...
Related tickets:
It's time to get hands on the review of the new Reports
Here I'm going to propose two alternatives, for Reproduction and Patch Testing.
Related tickets: