URL: https://bugfest-juniper.folio.ebsco.com/

Juniper release schedule

What	Who	When
Add test cases to R2 2021 (Juniper) TestRail test run	Product Owners	June 18, Friday
Folio module releases	Dev Teams	June 18, Friday
BugFest kick-off meeting	Testing Community	June 21, Monday
Claim test cases	Testing Community	June 21, Monday to June 27, Sunday
Complete BugFest Juniper system	EBSCO Hosting Team	June 23, Wednesday EOB
Bug Fest	Testing Community Product Owners	From July 12, Monday To July 23 , Friday
Bug Fixing	Dev Teams	July 26, Monday to August 6, Friday
R2 Juniper release becomes GA	Exec Team	August 16, 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:

Link to Juniper Bug Fest kick-off meeting video Use password "folio-lsp" to view it.

Bug Fest Instructions for Testing Community

We are using TestRail application for test case editing, assignments and execution tracking. https://foliotest.testrail.io
1. Helpful Resources page has links to training videos that will help to complete Bug Fest tasks.
2. Test case claim process is outlined in the similar named section in the Helpful Resources page
The test run Bug Fest R2 2021 July 12 to July 23 contains test cases that were assigned to this Bug Fest.
Folio URL to use: https://bugfest-juniper.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.
System has preconfigured users and permission sets.
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:
1. Testers don't file defects in Jira
2. 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

Test Rail Warning - If you need to add a test case to test run

Problem: While adding test cases to the existing Test Run original test case assignments are being reset.

Solution: The actual issue here is if the full test run was assigned to a user, when it is edited again in the future the assign to field will default to that user being selected in the dropdown, and when saved will re-assign all tests within to that user. The trick to prevent that from occurring would be to make sure that the "assign to" field is not set to that user's name, but instead it should be set to the blank entry at the top of the selection. This will keep all assignments to current users in tact when the edits are completed and saved.

View more detailed instructions in the Bugfix section of this page.

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
1. To link Jira bug to test case:
  1. Select test case
  2. Click "Add Result" button
  3. Enter Jira ID into Defects field (for example, UIU-999). Don't use URL format.
  4. Click "Save" button
2. Use mandatory label bugfest_R2.2021 for all logged defects.
3. Use label regression if functionality was working in prior release
4. Set Release field to "R2 2021 Bugfix" if bug must be fixed before Q3 2020 GA deadline.
5. 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=5210449
Jira Dashboard for R1 2021: https://folio-org.atlassian.net/secure/Dashboard.jspa?selectPageId=11808

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

Bug Fest R2 2021 Juniper