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

Honeysuckle release schedule

BugFest Goals

1. Execute complete test plan (see the scope table below). List of test cases can be found in the 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 Info:

• Time: October 19, 2020 09:00 AM Eastern Time (US and Canada)

• Zoom Meeting

  • Meeting ID: 818 3418 8799

  • Passcode: folio-lsp

  • https://us02web.zoom.us/j/81834188799?pwd=OG5KTWgrRUJlcjVWU3NNTEJqVXY1dz09

• Presentation deck

• Kick-off meeting recording  

  • Use password folio-lsp to watch the recording

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. Test case claim process is outlined in the similar named section in the Helpful Resources page

2. The test run Bug Fest Q3 2020 October 26 to October 30 contains test cases that were assigned to this Bug Fest.

   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.

3. Folio URL to use: https://bugfest-honeysuckle.folio.ebsco.com/
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. Please use deliverable email address when creating your user account 
6. FOLIO supports only Chrome as internet browser. Please do you testing in Chrome unless a test case description gives you specific instructions. 
7. 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
8. Please use Slack channel #bug-fest for all Bug Fest related communications
9. Retrospective meeting will be scheduled after the Bug Fest week.
10. List of participants: Folio Testing Community

Bug Fest Instructions for Product Owners 

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_q3.2020 for all logged defects.
   3. Use label regression if functionality was working in prior release
   4. Set Release  filed to  "Q3 2020  Bug Fix" if bug must be fixed before Q3 2020 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://folio-org.atlassian.net/wiki/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: https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=5210306

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