Test Ticket Queue 🎟
👉🏻 “(change: N)” represents changes from prior week (unless noted).
Current totals (change compared to 11 July):
- Needs reproduce issue: 1679 (change: -2)
- Patches needing testing: 200 (change: -5)
- Unit tests for patches:
- Tagged as needs testing info: 12 (change: +1)
New/changed in last 7 days:
- Needs reproduce issue: 8 (change: +1)
- Patches needing testing: 10 (change: +3)
- Unit tests for patches:
- Tagged as needs testing info: 3 (change: +2)
Closed in last 7 days:
- Could not reproduce issue: 1 (change: 0)
- Patches needing testing: 1 (change: -3)
- Unit tests for patches:
- Tagged as needs testing info: 1 (change: +1)
Query Adjustments 📣
What? The “Closed / Could not reproduce issue” query has been modified.
Why? The old query required keywords and milestones that do not relate to reproducibility, and returned inaccurate data (e.g. allowed tickets with fixed resolution).
Detailed changes to the query:
- Removes
needs-testingandhas-patchkeyword filters, as they do not pertain to reproducibility. - Removes milestone filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output., as this report does not focus on a specific release.
- Adds filter for resolution
worksforme, the close label for bugs that cannot be reproduced.
To discuss this or other queries used in this report, please comment below, or connect with the Test Team over in #core-test.