Bug Fest Instructions

1. We are using TestRail application for test case editing, assignments and execution tracking. https://foliotest.testrail.io
   1. If you are new the Test Rail it is recommended to watch the following videos to get familiar with the application:
      1. https://www.gurock.com/testrail/videos/introduction-projects - length 4:45 min
      2. https://www.gurock.com/testrail/videos/suites-test-cases - length 6:49 min
      3. https://www.gurock.com/testrail/videos/test-runs-results  - length 10:50 min
      4. https://www.gurock.com/testrail/videos/issue-defect-integration - length 4:37 min
2. Go to the Bug Fest test run and review test cases for your respective modules: https://foliotest.testrail.io/index.php?/runs/view/28&group_by=cases:section_id&group_order=asc&group_id=87

   Test Rail Warning

   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. Defects: 
   1. Use mandatory label bugfest_q3.2.2019 for all logged defects.
   2. Link to instructions how to create recordings on Mac if you are Windows user - feel free to use screen capture of your choice. 
6. Slack channel - "bug-fest"
7. 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.
8. Retrospective meeting will be scheduled after the BF week.
9. List of participants: Folio Testing Community

BugFest Scope

1. Execute complete test plan (see table below) List of test cases can be found here