Bug Fest Q3 2020 Honeysuckle
| Who | When |
|---|---|---|
Add test cases to Q3 2020 TestRail test run | Product Owners | October 19, Monday |
Folio module releases | Dev Teams | October 16, Friday |
BugFest kick-off meeting | Testing Community | October 19, Monday |
Claim test cases | Testing Community | October 19, Monday to October 23, Friday |
Complete BugFest Honeysuckle system | EBSCO Hosting Team | October 23, Friday |
Bug Fest | Testing Community Product Owners | October 26, Mondayto October 30, Friday |
Bug Fixing | Dev Teams | November 2, Monday to November 13, Friday |
Q3 2020 Honeysuckle release becomes GA | Exec Team | November 23, Monday |
BugFest Goals
Execute complete test plan (see the scope table below). List of test cases can be found in the test run:
100% of test cases with Critical or High priority should be completed
Add test case descriptions and steps if they are missing
Kick-off Meeting Info:
Time: October 19, 2020 09:00 AM Eastern Time (US and Canada)
Zoom Meeting
Meeting ID: 818 3418 8799
Passcode: folio-lsp
https://us02web.zoom.us/j/81834188799?pwd=OG5KTWgrRUJlcjVWU3NNTEJqVXY1dz09
Use password folio-lsp to watch the recording
Bug Fest Instructions for Testing Community
We are using TestRail application for test case editing, assignments and execution tracking. https://foliotest.testrail.io
Helpful Resources page has links to training videos that will help to complete Bug Fest tasks.
Test case claim process is outlined in the similar named section in the Helpful Resources page
The test run Bug Fest Q3 2020 October 26 to October 30 contains test cases that were assigned to this Bug Fest.
Folio URL to use: https://bugfest-honeysuckle.folio.ebsco.com/
Credentials: folio/folio. Please use this login to create a user with desired permissions that you will use for testing. Don't use "folio" user to run test cases.
Please use deliverable email address when creating your user account
FOLIO supports only Chrome as internet browser. Please do you testing in Chrome unless a test case description gives you specific instructions.
Failed test cases:
Testers don't file defects in Jira
When a test case fails, tester to create a comment in Test Rail for this test case and assign this test case to a Product Owner
Please use Slack channel #bug-fest for all Bug Fest related communications
Retrospective meeting will be scheduled after the Bug Fest week.
List of participants: Folio Testing Community
Bug Fest Instructions for Product Owners
Throughout the day, monitor failed test cases in your areas.
For each failed test case Product Owner reviews the problem, creates a Jira bug and links it to TestRail
To link Jira bug to test case:
Select test case
Click "Add Result" button
Enter Jira ID into Defects field (for example, UIU-999). Don't use URL format.
Click "Save" button
Use mandatory label bugfest_q3.2020 for all logged defects.
Use label regression if functionality was working in prior release
Set Release filed to "Q3 2020 Bug Fix" if bug must be fixed before Q3 2020 GA deadline.
Use the following Jira statuses to track bug progress:
Status | Indicator | Who | Action |
Awaiting bugfix release | Indicates the item needs a bugfix/hotfix release to be created | PO | Confirmed an issue in folio-snapshot |
Awaiting bugfix deployment | Indicates release containing bug fix is ready to deploy to BugFest environment | Lead Maintainer | Creates a module patch release from one or more PR |
In bugfix review
| Indicates the bug fix has been deployed to BugFest and is ready to test | Release Coordinator or QA Lead | Requests and verifies deployment of a module patch release to Bug Fest |
Closed |
| PO or tester | Verifies fix in Bug Fest |
Also monitor the Bugfest dashboard in JIRA for any bugs filed in your area (some testers and other POs may file bugs and we want to make sure we triage them, as well).
Assign a priority to your bugs according to the defect priority scheme https://folio-org.atlassian.net/wiki/display/DQA/Defect+Priority+Definition
Select a development team and notify the PO lead for the team so they can get development started
Follow the bug fix process outlined here: https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=5210306
Test Case Priority
Test cases that have Critical and High priority should be claimed first. Test Rail filter can be set to see test cases that have Critical or High priority.
Scope Table
Section is out of BugFest Scope |
Application | Test Cases | SME | Comments |
|---|---|---|---|
Users | Yes | @patty.wanninger |
|
Users - Patron Blocks | Yes | @Holly Mistlebauer |
|
Users - Search | Yes | @patty.wanninger |
|
Permissions | Yes | @Cate Boerema (Deactivated) @Anton Emelianov (Deactivated) |
|
Fees & Fines | Yes | @Holly Mistlebauer |
|
Inventory | Yes | @Charlotte Whitt |
|
Inventory - move | wip | @Charlotte Whitt |
|
Inventory - Search | Yes | @Charlotte Whitt | new test cases to be added (CW note 10/14/2020) |
Fast add | wip | @Charlotte Whitt |
|
Agreements | Yes | @Owen Stephens |
|
Licenses | Yes | @Owen Stephens |
|
eHoldings | Yes | @Khalilah Gambrell |
|
Requests | Yes | @Cate Boerema (Deactivated) |
|
Loans | Yes | @Emma Boettcher |
|
Check in | Yes | @Emma Boettcher |
|
Check out | Yes | @Emma Boettcher |
|
Circulation → Loan Policies | Yes | @Cheryl Malmborg |
|
Circulation → Loan Rules | Yes | @Cheryl Malmborg |
|
SIP2 | Yes | @Magda Zacharska | Not configured at Bug Fest environment |
Calendar | Yes | @Cheryl Malmborg |
|
Orders | Yes | @Dennis Bridges |
|
Organizations (formerly Vendors) | Yes | @Dennis Bridges |
|
Patron Notices | Yes | @Darcy Branchini |
|
Finance | Yes | @Dennis Bridges |
|
Invoices | Yes | @Dennis Bridges |
|
Receiving | Yes | @Dennis Bridges |
|
Data Import | Yes | @Ann-Marie Breaux (Deactivated) |
|
Data Export | Yes | @Magda Zacharska |
|
MARCcat | Yes |
|
|
Staff slips | Yes | @Darcy Branchini |
|
Settings > Locations |
| @Cate Boerema (Deactivated) |
|
Settings > Service points |
| @Cate Boerema (Deactivated) |
|
Tags | Yes | @Ann-Marie Breaux (Deactivated) |
|
Course Reserves | Yes | @Kelly Drake |
|
quickMARC | Yes | @Stephanie Buck |
|