Summary

Overall , we had much better executed test cycle this time. Retrospective meeting helped us to identify areas for improvement and we followed up on the identified action items. (Please see Q1 2019 retrospective page). We achieved much better coverage and completed practically all test cases that were planned.

Much better execution of BF Q1 2019 compare to Q4 2018:

We had 2 planning meetings before Bug Fest kick-off which helped with balanced task assignments.
Scope of the Bug Fest was defined upfront and included all the areas that were not covered in Q4 2018
Test environment data was prepared much better and was matching the original Chalmers system.
We didn't run into significant performance issues.
Practically all planned test cases has been executed.
Much smaller percentage of defects has been dismissed compare to Q4 2018. 11 defects out of 76 (or 14%) compare to 38 defects out of 85 (or 45%).
Pass/Fail results can be found here

Here are the highlights of the results:

76 defect has been logged over the course of 5 days.
Only 11 defects has been closed as "duplicate", "cannot reproduce", or "won't do". We did much better this time because every test case had notes provided by PO. These notes helped to set the right context for each test case.
50 defects has been added to various teams backlogs. Core Functional team has the most of them - 48.
Defects were submitted by 13 different participants (admin, POs, regular testers, library staff).
Testers logged the most number for defects against ui-users, ui-inventory, ui-requests, ui-checkout, ui-circulation, and ui-eholdings modules (please see chart below.)
Link to the live JIRA dashboard is here

Browser not supported