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) by Sept 1st.
-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.
- We would love for 2 institutions to commit to upgrading in production system before wide-release but realize this is hard.
- Minor release should have less process?
- update the 2 document
- new features should be tested
- how thoroughly do all features need to be tested?
Accessibility should be it's own test - wave should at least be done, consult with Michael and Tribune.
UI interaction
- What is in Hyrax 2 and when can we get it.
Before the testing tracking document we need to complete UI interaction and answer these questions
- Tracking documents.
- What browsers and platforms should be included? Poll repo-managers at least.
- End User tools
- OS
- Windows 7 +
- OS10
- Mobile platforms for what? Would it hold up a release?
- Android version?
- IOS version?
- OS
- Admin and staff tools
- OS
- Window 7 +
- OS10?
- Mobile not needed
- OS
- Chrome, Safari, Firefox, IE, Edge (for end users), Opera (for end users?), mobile browsers (for end users?)
- End User tools
- What browsers and platforms should be included? Poll repo-managers at least.
To do's: by Aug 18th
Ask repo-managers what platforms and OS should be tested/supported
Ask Michael/Kate testing for accessibility
Develop a list of features to be included in 2.0
Chris does 1.3 walkthrough
Finish a template for the testing document,
- Add instructions for how to use the document -Sherry
- Mirror the structure and organization of the UI Interactions documents.
Bug reporting template.