BugFest start date has been delayed by 2 days.

New start date is Wednesday, December 11th.

Please watch bug-fest channel for the latest status.

Bug Fest Process and Important Dates:

BugFest Goals

1. Execute complete test plan (see the scope table below). List of test cases can be found in the test run: Bug Fest Q4 12/9/19 - 12/13/19
2. 100% of test cases with Critical or High priority should be completed
3. Add test case descriptions and steps if they are missing
4. Add Jira links to test cases for user stories that are related to these test cases. 

Kick-off Meeting Info

Time: Dec 2, 2019 09:00 AM Eastern Time (US and Canada)

https://zoom.us/j/803838823

Meeting ID: 803 838 823

https://zoom.us/recording/share/BM3EkvETX1nnAHyCzsmJBbOPmFlovf3KVd4x-7_WbSmwIumekTziMw 

scroll to 7:40 for the start of the meeting. 

One tap mobile

+16468769923,,803838823# US (New York)

+16699006833,,803838823# US (San Jose)

Dial by your location

+1 646 876 9923 US (New York)

+1 669 900 6833 US (San Jose)

Meeting ID: 803 838 823

Find your local number: https://zoom.us/u/auj7f6oLm

Bug Fest Instructions

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 Q4 12/9/19 - 12/13/19 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 to the blank entry at the top of the selection. This will keep all assignments set to their current users when the edits are completed and saved.

3. Folio URL to use: https://bugfest.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 scenarios.
5. Please use deliverable email address for your user
6. FOLIO supports only Chrome as internet browser. Please do you testing in Chrome unless a test case description gives you specific instructions. 
7. Defects: 
   1. Use mandatory label bugfest_q4.2019 for all logged defects.
   2. If you want to attach a video recording that shows how to replicate a bug you could use:
      1. This Link to instructions how to create recordings on Mac by using QickTime.
      2. if you are Windows user - feel free to use screen capture of your choice. However, Jing tool work pretty well on Windows. 
8. Slack channel - "bug-fest"
9. Bug triage - we'll be triaging bugs daily to make sure that P1 and P2 bugs treated with the proper urgency and fixed before Q2 is out. This is done by Product Owners.
10. Retrospective meeting will be scheduled after the Bug Fest week.
11. List of participants: Folio Testing Community

Test Case Priority

Test cases that have Critical and High priority should be claimed first. TestRail filter can be set to see test cases that have Critical or High priority.

Currently, the following sections of the test plan have these test cases:

• Users
• Fees & Fines
• Permissions
• Requests
• Orders
• Finance 

Scope Table