Retrospective - Bug Fest Q2.1 2019
- Anton Emelianov (Deactivated)
Owned by Anton Emelianov (Deactivated)
FEEDBACK:
- Follow this link to the Bug Fest Retrospective board  and post your Feedback.Â
- Please add your comments, thoughts, ideas to "Went well" and "To improve" columns.
- If you like or agree with comments of the other contributors please don't hesitate to give them your vote of approval by clicking on the "thumbs up" button.
- If you have any questions, please post them into Questions column. The answers will be provided during Retrospective meeting and subsequently on this page. Â
MEETING INFO:
SLACK CALL on bug-fest channel 9 to 10 AM, Friday 6/7; New York Time. (check your local time)
BFQ4-18 ACTION ITEMS STATUS :
| Action Item | Status | Add to Playbook |
|---|---|---|
Make sure that performance issues are reported separate | "performance" label was used | |
Use TestRail instead of the Google Spreadsheet | DONEÂ | |
Transfer test cases into TestRail | DONE | |
Provide TestRail training | DONE | |
PO to improve test case descriptions | ||
Post module/PO mapping before BF start for testers to post direct questions to the right person | NOT DONE | |
Call separate meeting on the bug triage and handling workflow. | DONE | |
PO should NOT test a module that they are working on | ||
Start BF on Tuesday - Don't start on Monday | Started on Thursday |
ACTION ITEMS
Action items were aggregated from the retrospective board:Â
- Create reference data checklist
- Publish reference data for every Bug Fest.Â
- Participants to actively add information to test cases to help future testers execute the same test case.
- Rethink how test run is being created and managed.