Table of Contents

Bugfest Test Environment

...

1. Execute the complete test plan (see the scope table below). A list of test cases can be found in the Bugfest: R2 2024 Ramsons
2. 100% of test cases with Smoke, Critical or Extended High priority should be completed
3. Add test case descriptions and steps if they are missing

Kick-off Meeting Links

• Recording

  - TBA

• Presentation 

Bug Fest Instructions for Testing Community

1. We use the TestRail application to edit test cases, assignments, and status execution. Folio Bug fest Project under https://foliotest.testrail.io
   1. Helpful Resources page has links to training videos to help complete Bug Fest tasks.
   2. The similarly named section on the Helpful Resources page outlines the test case claim process.
   3. Review Kick-off meeting links when necessary. 

2. R Release Test Run  contains test cases assigned to this Bug Fest. (Useful link: all test cases are sorted by priority, then set the filter to "Untested" to find unclaimed ones)

   1. Priorities can be seen on the right side. Our approach is to claim/execute tests in the following order. Smoke, Critical Path, and then Extended.
   2. Since many tests are in Extended, we recommend running Extended as a high priority first. 
      1. To get extended high-priority tests - Click on the right side for Extended and Select in the Filter bar, select, Prioritization = Critical and High
      2. For Extended low priority, please filter Priortization = Medium and Low
3. Please use the folio user login to create a user with the desired permissions you will use for testing. Don't use the "folio" user to run test cases.
4. The system has preconfigured users and permission sets. 
5. Please use the deliverable email address when creating your user account 
6. FOLIO supports only Chrome as an internet browser. Please test in Chrome unless a test case description gives you specific instructions. 
7. Please review Bugfest testing details table and Known Issue table on this page
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. See Scope table below with list of POs assigned to app or module. Include screenshots are very helpful. 
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 you no longer want to participate.

...

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

...

...