FEEDBACK:
- Meeting will be scheduled between Thursday 3/14 and Friday 3/22.
- Go to LettuceMeet and post your availability
- Please be aware that 9 to 5 time on the schedule is in the Eastern Daylight Savings time zone.
- 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, Wednesday 3/20; New York Time. (check your local time)
BFQ4-18 ACTION ITEMS STATUS :
| Action Item | Status |
|---|---|
Consider to use TestRail for subsequent Bug Fest runs | Will be used in BF Q2 2019 |
Not all the areas of FOLIO were covered. Do next BF soon to cover them. | DONE Coverage over 99% in BF Q1 2019 |
| Better scope definition is needed to avoid testing incomplete features. | DONE |
| Always use real customer data. | DONE |
| Original reference data must be migrated to the BF environment. | DONE |
| Must have a planning meeting for every BF run: Define scope; Assign tasks to make sure that participants have time to complete them. | DONE |
Test cases for each module need to be reviewed with respective POs | DONE |
| Discussion is needed about how long BF environment is staying up after test run is over. | TBD |
| Discuss what should be bug workflow for the future BF runs. | TBD |
ACTION ITEMS
Action items were aggregated from the retrospective board:
Q&A: