2022-07-26 Acquisitions Meeting notes

Owned by Heather McMillan
Last updated: Jul 26, 2022
2 min read

Date

Attendees


Ann Crowley, Bill Verner, Dennis Bridges, Dung-Lan Chen, Dwayne Swigert, Emily Robertson, Heather McMillan, Jackie Magagnosc, Jean Pajerek, Julie Branon, Julie Stauffer, Kathleen Norton, Kristin Martin, Lauren Seney, Linh Chang, Lisa Maybury, Lisa Smith, Lloyd Chittenden, Lucinda Williams, Martina Schildt, Masayo Uchiyama, Michael Philips, Nancy Pelis, Okay Okonkwo, Sara Colglazier, Scott Perry, Steve Selleck, Tara Barnett, Victoria Anderson, Winter White

Agenda


Current: Tuesday, July 26, 2022

Housekeeping -

  • reminder - next meeting this Friday (7/29) at 9 am EST

Business - focusing on Morning Glory Bugfest

    • Dennis will demo how to login to test rails to claim test cases and how to complete one as show and tell
    • Bring any questions you might have regarding bugfest that Dennis will help address
    • If enough time left, the group can sign in (or sign up) test rails and claim a test case or two of your own (smile)

FOLIO bugfest runs Monday July 18 through Friday July 29. Details - https://folio-org.atlassian.net/wiki/display/FTC/Bug+Fest+R2+2022+Morning+Glory
What is bugfest? FOLIO community’s testing of the upcoming release features.
Who participates in bugfest? Anyone can participate. To do so:
1. Request to join the FOLIO bugfest slack channel. Send me an email or Teams message.
2. Request a Testrails account. Contact Anton (v-aemelianov@ebsco.com).
3. Claim a test case(s) -(https://foliotest.testrail.io/index.php?/runs/view/2037&group_by=cases:section_id&group_order=asc )
4. During July 18 - July 29, please allocate time to test. If you cannot test please unassign yourself ASAP from the test so that someone else can take the test case.
Please do not wait until the last minute to test because it means less time for development teams to resolve any issues.

Discussion items

TimeItemWhoNotes
:02BugfestDennis
  • Dennis demonstrated how to participate in testing. 
  • Test cases are based on what has been developed. 
  • Dennis has created filters to be able to only see test cases related to Acquisitions. 
  • There are still about 50 or 60 Acquisitions test cases that have not been claimed by a user. 
  • So steps to test
    • Get a user account 
    • Claim test cases. 
      • No one else can work on it while you have it claimed. 
      • Test, then add result saying it passed or failed. 
      • If once you start trying to test a case you claimed, if you realize you are not going to be able to do it, go back and un assign it. 
      • If you fail a test case, it is helpful to go step by step to show where it failed. 
      • You can add screen shots to your result and/or a video of what happened.
  • From Julie Brannon (she/her) to Everyone 12:06 PM
    I received this question from a new tester this week:  If they see something inaccurate in the instructions for the test, how would you want to receive that feedback?  It doesn't seem appropriate to "fail" the test.  I advised using the "+Add Comment or file" to assign a comment on the test and assign it to the PO.  Does that sound good?
    • Yes
  • From Lloyd Chittenden to Everyone 12:19 PM
    @Julie, I think that incomplete documentation should count as a fail. Documentation needs to be integral to the product. That should be part of the test.
    • If it is unclear, it is ok to fail the test. 
  • From duchen to Everyone 12:25 PM
    Dennis, can you view the instructions before claiming a case?
    • Yes




Action items

  •