Goal:

Create appropriate descriptions, steps, and expected results for test cases to be used during Bug Fest events. We expect the Testing Community membership will be rotating as organizations complete their implementations of FOLIO.

That being said, having solid test cases will make it easier for new testers to participate. We can also expect improvements in test results reliability as very few things should be left to interpretation.

Communication

via Slack channel "test-cases" 

Deadlines:

• Testers to claim test cases - October 25
• PO to claim remaining test cases - November 1
• Testers to submit test cases for PO review - November 15
• Final deadline: December 2

Test Cases Location

Test cases for this project are located at: https://foliotest.testrail.io/index.php?/suites/view/21  

Test Run:

All work will be tracked in the following test run:

https://foliotest.testrail.io/index.php?/runs/view/55

Participants:

• Product Owners - They will be responsible for:
  • reviewing every test case that has descriptions, steps, and expected results.
  • providing feedback to testers on test cases submitted by them
  • creating content for for test cases with complex scenarios 
  • approving test cases for Testing Community use. 
• Testers - They will be responsible for:
  • creating descriptions for test cases that were completed by testers during Bug Best 3.2
  • creating test cases descriptions for sections of FOLIO where testers have a high degree of confidence or familiarity.
  • submitting test cases to product owners for review.

Statuses

TestRail statuses will have different meaning during this exercise:

• FAILED - Testers can claim any test case in this status. After October 25 all test cases that hasn't been claimed will be transitioned to UNASSIGNED.
• UNASSIGNED - test cases that were net claimed by testers by October 25. PO will need to claim them and create test case descriptions themselves.
• RETEST - this status is PO 's inbox. After testers complete test case description they should transition status from FAILED to RETEST and assign this test case to a PO for related module.
• PASS - PO will change test case status to PASS when test case description has been:
  • created by tester or PO
  • reviewed by PO
  • approved by PO
• BLOCKED - no particular meaning has been assigned to this status for this exercise. 

Product Owners and FOLIO Modules