Test team update for 27 Sep 2021

Test Ticket Queue

(change: N) represents changes from last week = this week – last week

Current totals:

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

New/changes In last 7 days:

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

Closed in last 7 days:

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

Highlights

  • Week in Test => curated guide to point testers were they could contribute this week; also includes posts for awareness and learnings
  • Modernize to Latest PHPUnit project is now complete 🎉
    • Dev Note published
    • Huge kudos to cross-team, cross-component, and cross-(open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL.)project effort to solve this hard hard problem and each challenge! 👏 Showed the best of our collaborative spirit 🎉
  • Core e2e working strategy session happening this week (i.e. for 5.9 testing roadmap)

Help needed:

  • Need help broadly reaching extenders who are impacted (i.e. those who run their integration tests using coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s test framework)
  • #test