1 of 13

Kick-off Meeting

Bug Fest Morning Glory

R2 2022

15th Edition

| www.folio.org

1

2 of 13

BugFest Goals

Execute complete test plan in TestRail.

100% of test cases with Critical or High priority should be completed
Add test case descriptions and steps if they are missing.

| www.folio.org

2

3 of 13

Preparation before Bugfest (1/3)

1. Join #bug-fest channel in Slack (folio-project.slack.com)�- It’s a private channel: Ask someone who is already in it, to add you.

2. Check if you have a Wiki account - https://wiki.folio.org/�- If not, get one here: https://issues.folio.org/secure/Signup!default.jspa�(Yes, the account you create there will indeed work with Confluence)

4. Add your name to the Testing Community Membership page: https://wiki.folio.org/display/FTC/FOLIO+Testing+Community+Members

Remove your name if you don’t want to be invited to the next Bug Fest.

3. Check you have a TestRail account: https://foliotest.testrail.io/� - If not, contact @anton_e (v-aemelianov@ebsco.com) � - No login for past 6 month → Account may be disabled.� Contact @anton_e

| www.folio.org

3

4 of 13

Preparation before Bugfest (2/3)

4. Claim tests the week before Bugfest: July 11 through July 17

Direct link to test run: https://foliotest.testrail.io/index.php?/runs/view/2037
Please claim tests in the test run Bug Fest Morning Glory (R2 2022)
Do not claim test cases in test runs called:
Bug Fest Morning Glory AUTOMATED (R2 2022)
Bug Fest Morning Glory MULTI-TENANT (R2 2022)
Claim test cases with Critical and High priority first.
Only claim what you are sure you can complete on time!
Don't take away a test case that has been claimed by someone else. Reach out to the current assignee first before taking away a test case.�

Video: How to claim a test case

| www.folio.org

4

5 of 13

Bug Fest Test Run in TestRail (Manual)

https://foliotest.testrail.io/index.php?/runs/view/2037

Morning Glory release has 1954 test cases vs 1632 in Lotus; 322 additional.
Claim your test cases early - Monday, Tuesday, Wednesday
EPAM testers will start claiming on Thursday, July 14

| www.folio.org

5

6 of 13

Preparation before Bugfest (3/3)

5. Create your test user in the test environment: �https://bugfest-mg.int.aws.folio.org/

Use these credentials first: folio/folio. Then create a user with desired permissions that you will use for testing.
Users from Lotus Bug Fest will be retained.
Don't use "folio" user to run test cases.
Use deliverable email address when creating your user account.
FOLIO supports only Chrome as internet browser.�
Technical staff may take the system down any time in order to fix a blocking problem. Information will be posted in #bug-fest.

| www.folio.org

6

7 of 13

During Bugfest (1/2)

1. Complete the test cases during Bugfest: July 18 through July 29�Direct link to test run: https://foliotest.testrail.io/index.php?/runs/view/2037�- Please try to test as much as possible during the first week.�- When the test is successfully completed, set the test to Passed:��

�2. Keep community informed if you are falling behind on your commitment:�- Please try to give warning as early as possible. �- Don't leave claimed but uncompleted test cases behind. �- Seek help by posting in #bug-fest Slack channel.

| www.folio.org

7

8 of 13

During Bugfest (2/2)

3. When a test case fails:

1- Assign this test case to a Product Owner (find PO in the Scope table): https://wiki.folio.org/display/FTC/Bug+Fest+R2+2022+Morning+Glory

2- Create a comment in TestRail for this test case:�

3- Reach out to PO directly to tell them.

| www.folio.org

8

9 of 13

Schedule

What	Who	When
Add test cases for Morning Glory release	Product Owners	May 27, Friday
Folio module releases	Dev Teams	July 8, Friday
BugFest kick-off meeting	Testing Community	July 11, Monday
Claim test cases	Testing Community	July 11, Monday to July 17, Sunday
Complete BugFest Lotus system	Kitfox DevOps Team	July 13, Wednesday EOB
Bug Fest	Testing Community Product Owners	July 18, Monday to July 29, Friday
Bug Fixing	Dev Teams	August 1, Monday to August 12, Friday
Morning Glory (R2 2022) release becomes GA	Exec Team	August 22, Monday

https://wiki.folio.org/pages/viewpage.action?pageId=79468624

| www.folio.org

9

10 of 13

Bug Fest Environment Requests

Request types:

Deployment
Performance Issue
Functional

Post your request in #bug-fest or create Jira ticket in Bug Fest Jira project (BF)
Requestor will be added as a watcher to the ticket (if you have Jira account)

| www.folio.org

10

11 of 13

Product Owners

Throughout the day, monitor failed test cases in your sections.
For each failed test case Product Owner: 1) reviews the problem 2) creates a Jira bug 3) links test case to Jira bug ( add Jira ID into Defects field). Don't use URL format.
Use mandatory label bugfest_R2.2022 for all logged defects.
Use label regression if functionality was working in prior release
Set Release field to Morning Glory R2 2022 Bug Fix if bug must be fixed before Q1 2022 GA deadline.
Use the following Jira statuses to track bug progress:

Status	Who	Action
Awaiting bugfix release	PO	Confirmed an issue in folio-snapshot
Awaiting bugfix deployment	Lead Maintainer	Creates a module patch release from one or more PR
In bugfix review	RC or QA Lead	Requests and verifies deployment of a module patch release to Bug Fest
Closed	PO or tester	Verifies fix in Bug Fest

| www.folio.org

11

12 of 13

Helpful Links

Testing Community home page: https://wiki.folio.org/display/FTC/FOLIO+Testing+Community

Bug Fest Instructions page: https://wiki.folio.org/display/FTC/Bug+Fest+R2+2022+Morning+Glory

Test Environment: https://bugfest-mg.int.aws.folio.org/

TestRail test run: https://foliotest.testrail.io/index.php?/runs/view/2037

Slack #bug-fest

Jira Dashboard https://issues.folio.org/secure/Dashboard.jspa?selectPageId=12403

Testing Community Membership: https://wiki.folio.org/display/FTC/FOLIO+Testing+Community+Members

Training videos https://wiki.folio.org/display/FTC/Helpful+Resources

| www.folio.org

12

13 of 13

Questions?

| www.folio.org

13