Purpose:
- Working with Samvera community, develop a process for ensuring Hyrax releases are stable and tested.
Goals:
- To understand all of the features in Hyrax releases and document them.
Google Hangout: https://hangouts.google.com/hangouts/_/c4dvatljlzeofeapgzlljsok2ie
Members:
Consults:
Michael Joseph Giarlo - dev team
Jenn Colt - ux team
Michael Tribone and Kate Deibel said they were willing to consult on process for accessibility testing.
Documents:
- UI interactions
- Hyrax testing process proposal
- UI testing tracking document (Example of a potential model, only)
Questions:
Why not automate, why human testing?
What about UX and accessibility?
Meeting notes:
To do list:
Complete UI Interactions documents - Hyrax 2.0
-How do we do this before sandbox?
-Decide and Audience
-1.3. walkthrough - Chris (mark features that are not in 1.3, add missing interactions)
-We want to make this a manual that explains all the features, and admin.
-Format: categories seem good, the repeating the work interaction is distraction.
-Needs more examples, that address Use this for examples.
Release Testing Process:
- Need bug reporting template.
- What is a time frame that is acceptable for returning results of test? (2-3 weeks)
- The turn around time for updating the 2 important documents
- We think we need 3 institutions to commit to this work for each release ahead of time. Would be good to rotate these institutions.