Test Team Update for 21 March 2022

Test Ticket Queue

(change: N) represents changes from last week (unless noted)

Current totals (change is compared to 7 March):

Needs reproduce issue: 1587 (change: +12)
Patches needing testing: 208 (change: -7)
Unit tests for patches:
- Need unit tests: 121 (change: -1)
- Have unit tests & need review: 150 (change: -6)
Tagged as needs testing info: 11 (change: 0)

New/changes In last 7 days:

Needs reproduce issue: 9 (change: -9)
Patches needing testing: 7 (change: +7)
Unit tests for patches:
- Need unit tests: 0 (change: 0)
- Have unit tests & need review: 6 (change: -1)
Tagged as needs testing info: 0 (change: 0)

Closed in last 7 days:

Could not reproduce issue: 0 (change: -5)
Patches needing testing: 0 (change: -5)
Unit tests for patches:
- Need unit tests: 0 (change: 0)
- Have unit tests & need review: 5 (change: +3)
Tagged as needs testing info: 0 (change: 0)

Big picture goal: fuel the feedback loops back into the development process to identify what does and does’t work as expected for iteration as early as possible.
4 initiatives were identified. Planning and top priority groundwork are underway.
- Initiative 1: Improve the testing suite to (a) provide feedback that covers both expected and unexpected behaviors / results and (b) improve stability, readability, and ease of contributing.
- Initiative 2: Ensure all patches ready for commit have tests.
- Initiative 3: Grow the e2e test suites.
- Initiative 4: Improve the Testing Handbook to make it empower anyone who wants to test to quickly get testing.