Bug Fest Q2.1 2019 Report

Owned by Anton Emelianov (Deactivated)
Last updated: Jun 09, 2019

Summary

We were expecting much higher escaped defect count. Absence of P1 and only few P2 came in as a very pleasant surprise. Our focus on building unit test code coverage is starting to pay off. Even though that we're way far from being done, the positive trend is emerging slowly. 

 

Bug Fest notes:

  • Bug Fest team had only 1 planning meeting but it was sufficient.
  • We used Test Rail application to manage test cases and track Bug Fest execution.
  • All functional areas has been covered except Loan Policies that we not high on priority list for Chalmers. 
  • We didn't run into significant performance issues. 
  • We did our best to triage and move defects to respective team backlogs.
  • Similar to BF Q1 2019, test environment was created on time and we didn't incur major environment or data issues during test cycle.
  • Much smaller percentage of defects has been dismissed:
    Bug Fest%
    Q4 201845%
    Q1 201914%
    Q2.1 201911%

Highlights of the results:

  • 36 defect has been logged over the course of 5 days.
  • Only 4 defects has been closed as "duplicate", "cannot reproduce", or "won't do".  This is much better that the previous run.
  • 31 defect has been added to various teams backlogs. Core Functional team has the most of them - 16. Considering that it had 48 during previous Bug Fest Q1 2019, it's a big improvement.
  • Defects were submitted by 7 different participants (admin, POs, regular testers, library staff)
  • Testers logged the most number for defects against ui-inventory (please see chart below)
  • Overall, only a few defects has been filed against each module.
  • Out of 36 total defect 9 were related to testing FOLIO permissions. Most of these defects are P3 and are not blocking Q2 release.
  • Link to the live JIRA dashboard is here