Story Reviews

Story reviews are a type of manual testing.  The goal of this testing is to review completed user stories and bug reports in JIRA to verify that stated requirements are met.  Focus is on identifying failed requirements.  This type of testing must be coordinated with the FOLIO core team.  Please contact Cate Boerema for more information.

Process

1. You will need a JIRA account.  Please sign up here and then contact Cate for the ability to edit (standard access is view-only).
2. Review JIRA items where Status = In Review.  This status indicates the issue is dev-complete and ready to test.  
3. Pick any issue (story, bug, task etc) that is understandable and looks like something you can review.  Occasionally, you will find a technical issue in this list that isn't obviously testable - these can be ignored.
4. Review the issue requirements (scenarios in the case of a user story, steps-to-reproduce in the case of a bug report) and test to verify that the requirements are met
   1. If there is a failed scenario or other issue with a user story:
      
      1. Change the story status from In Review to In Progress
      2. File a bug in the same project as the original story
         1. You might want to scan the Bugs filter for recently filed bugs to make sure there isn't already a bug created
         2. Please use the standard bug format
      3. Assign the bug to the assignee from the original issue
      4. Link the bug to the original story (the bug "blocks" the original issue)
   2. If there are many failed requirements on a user story - Sometimes a story that is marked In Review has many immediately observable problems.  Rather than creating many JIRA bugs,
      
      1. Note the issues you are seeing in the comments section of the original JIRA issue and ask the developer (assignee) if you should create separate bugs for each of the issues.
      2. Change the story status from In Review to In Progress
   3. If a bug fix doesn't address the problem stated in the bug report you are testing:
      1.  Change the bug status to In Progress
      2. Add a label with the current sprint, to ensure the reopened bug comes up in the developer roundup meeting. You can get the current sprint number from the FOLIO team calendar.
      3. Note the issue you are seeing in the bug comments section
5. When the developer has addressed the bug(s) you filed, they will:
   1. Mark the bug In Review so it can be tested
   2. Mark the original story In Review so it can be tested
6. When an issue passes test:
   1. Leave a simple comment like "Tested and closing as done"
   2. Change the status to Closed > Done

Additional Info

• If you have questions about the requirements described, you can ask them in the comments section of the issue and the issue author or developer will answer.
• If, in the process of testing, you come across a bug that is unrelated to the issue requirements, please follow the process for exploratory testing.
• For stories with scenarios, it is often helpful to indicate the passed and failed scenarios using icons, as seen in this screenshot: