URL: https://bugfest-nolana.int.aws.folio.org

Nolana release schedule

BugFest Goals

1. Execute the complete test plan (see the scope table below). A list of test cases can be found in the Bug Fest Nolana (R3 2022) test run
2. 100% of test cases with Critical or High priority should be completed
3. Add test case descriptions and steps if they are missing

Kick-off Meeting Links

• Recording

• Presentation deck 

Bug Fest Instructions for Testing Community

1. 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. The test case claim process is outlined in the similarly named section on the Helpful Resources page

2. The test run Bug Fest Nolana (R3 2022) contains test cases that were assigned to this Bug Fest.

3. Folio URL to use: https://bugfest-nolana.int.aws.folio.org
4. 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.
5. The system has preconfigured users and permission sets. 
6. Please use the deliverable email address when creating your user account 
7. FOLIO supports only Chrome as an internet browser. Please do your testing in Chrome unless a test case description gives you specific instructions. 
8. Failed test cases:
   1. Testers don't file defects in Jira
   2. When a test case fails, a tester creates a comment in Test Rail for this test case and assigns this test case to a Product Owner
9. Please use Slack channel #bug-fest for all Bug Fest related communications
10. A retrospective meeting will be scheduled after the Bug Fest week.
11. List of participants: Folio Testing Community.
    1. Add yourself to the list if you want to participate in future BugFest events.
    2. Remove yourself from the list if don't want to participate any longer.

Bug Fest Instructions for Product Owners 

To include a test case in the Bug Fest test run - set the "Test Group" field to:

• Smoke
• Critical Path
• Extended

To remove the test case from the Bug Fest test run - set the "Test Group" field to:

• Draft
• Obsolete
• Automated

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

1. Throughout the day, monitor failed test cases in your areas.
2. 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_R3.2022 for all logged defects.
   3. Use label regression if the functionality was working in the prior release
   4. Set the Release field to  "Nolana R3 2022 Bug Fix" if the bug must be fixed before Q2 2022 GA deadline. 
   5. Use the following Jira statuses to track bug progress:  

1. 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).
2. Assign a priority to your bugs according to the defect priority scheme https://wiki.folio.org/display/DQA/Defect+Priority+Definition 
3. Select a development team and notify the PO lead for the team so they can get development started
4. Follow the bug fix process outlined here: Nolana (R3 2022) PO Bugfix and Hotfix Release Process
5. Jira Dashboard for R2 2022: 

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