Environment Details

URL: https://bugfest-poppy-consortium.int.aws.folio.org/

Please log In using the admin account and create a user in the correct tenant depending on your test case. IMPORTANT: Please watch this video on how to create a user. 

Poppy ECS bug fest environment update will be triggered 2 times a day(based on the availability of new releases):

1. 4-30 am ET
2. 12-00 pm ET

Note:- Poppy (R2 2023) Bugfest environment preparation plan

Poppy release schedule

BugFest Goals

1. Execute the complete test plan (see the scope table below). A list of test cases can be found in the Bug Fest Poppy (R2 2023) (ECS Enabled) 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 Links

• Recording

• Presentation deck 

Bug Fest Instructions for Testing Community

1. We use the TestRail application for test case editing, assignments, and execution tracking. 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.

2. Bug Fest Poppy's test run contains test cases assigned to this Bug Fest. (Useful link: all test cases sorted by priority, then set filter to "Untested" to find unclaimed ones)

3. Folio URL to use:
4. Credentials: ecs_admin/admin Please use this login to create a user with the desired permissions you will use for testing. Don't use the "folio" user to run test cases.
5. The system has preconfigured users and permission sets. 
6. Please use a deliverable email address when creating your user account 
7. FOLIO supports only Chrome as an internet browser. Please test in Chrome unless a test case description gives you specific instructions. 
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.
9. Please use Slack channel #bug-fest-ecs 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.

Bug Fest Instructions for Product Owners 

To include a test case in the Bug Fest test run - set the "Test Group" field to:

• Smoke
• Critical Path
• Extended

To remove the test case from the Bug Fest test run - set the "Test Group" field to:

• Draft
• Obsolete
• Automated

View more detailed instructions in the Bugfix section of this page.

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_ecs_R2.2023 for all logged defects.
   3. Use label regression if the functionality was working in the prior release
   4. Set the Release field to  "Poppy R2 2023 Bug Fix" if the bug must be fixed before Q4 2023 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 ensure we triage them, too).
2. Assign a priority to your bugs according to the defect priority scheme - /wiki/spaces/DQA/pages/2657909
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:
5. Poppy R2 2023 Dashboard (Jira)

Test Case Priority

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

Scope Table

Known Issues

• Additional issues are posted on the official release notes page