Bugfest Test Environment

...

What	Who	When
Add test cases for the Ramsons release	QA Team	Oct 25th, Friday
Folio module releases	Dev Teams	Oct 31st, Thursday
BugFest kick-off meeting	Yogesh Kumar	Oct 30th, Wednesday
Claim test cases	Testing Community	Oct 31stNov 6th, Thursday Wednesday - November 8th11th,FridayMonday
Complete BugFest system	Kitfox DevOps Team	November 6th, Wednesday
Bug Fest	Testing Community Product Owners	November 11th, Monday - November 29th, Friday
Bug Fixing	Dev Teams	November 29th - December 5th
Ramsons (R1 2024) release becomes GA	Exec Team	December 16th, Monday

...

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

Kick-off Meeting Links

Recording
Presentation

Bug Fest Instructions for Testing Community

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.
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
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.
The system has preconfigured users and permission sets.
Please use the deliverable email address when creating your user account
FOLIO supports only Chrome as an internet browser. Please test in Chrome unless a test case description gives you specific instructions.
Please review Bugfest testing details table and Known Issue table on this page
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.
Please use Slack channel #bug-fest-ecs or loc-phase-1-testing for all Bug Fest-related communications
A retrospective meeting will be scheduled after the Bug Fest week.
List of participants: FOLIO Testing Community ECS , and FOLIO LOC.
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.

...

Throughout the day, monitor failed test cases in your areas.
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:

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 JIRABugfest 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 - /wiki/spaces/DQA/pages/2657909
Select a development team and notify the PO lead for the team so they can get development started
Follow the bug fix process outlined
Quesnelia R1 Ramson R2 2024 Dashboard

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.