Bug Fest Q1 2020 Retrospective Report


1	Keep testers not to file bugs	It works really well. Testers have more time for testing
2	Ran participation report before and after Bug Fest	Test cases can get reassigned multiple times. Anton did his best to get participation counts right. There were confirmed before publishing the results.
3	Make sure that process is set and communicated before Bug Fest	Process was documented and timely updated at the release page
4	Keep deploying bug fixes 2 times a day	Done
5	Settle P1 and P2 defects with capacity planning group during bug fest	All P1 and P2 defects are closed except 1 P2 bug
6	Release Coordinator	Oleksii Petrenko was introduced as release coordinator. He implemented many valuable process changes that allowed us to manage and control the release process much better.
7	Lack of integration testing. Figure out environment to develop with.	Scratch environments are available in Q3; Karate integration tests implementation is WIP in Q3. DevOps improvements to track both Karate and Postman tests.
8	Log aggregation application is needed	Easy access to BUg Fest logs was enabled at https://folio-bugfest-logs.s3.amazonaws.com/exportedLogs. Still need to implement log aggregation solution.
9	Schedule meetings with Devs to review root causes of regressions	WIP. https://docs.google.com/presentation/d/1DSD-ymmn4wRpQL5TRvgFepeGuL0PKNGPSxGXfs4zqRM/edit?usp=sharing
10	Anton to figure out how to filter out new test cases in Test Rail and execute them outside of Bug Fest	No action.
11	Anton to do abetter job coordinating data loading	We used the same dataset and migrated it from Flameflower to Goldenrod. Therefore we had much fewer problems with test data.