Overview
The testing subteam accomplished the following in the previous year
Regression Testing for the 3.1.0 and 3.2.0 releases
Tested or are currently watching 71 specific JIRA issues
Led discussion on the work of the testing subteam, how community members can get involved in testing activities, and testing and maintenance practices at local institutions for 2022 Online Forum.
What Went Well
As in previous years, we managed to accomplish all of the requested testing within the timeframes assigned for each group of features or release. There were a few occasions when some team members were unavailable, but everyone pitched in to make sure we got the testing done on time.
This year we held optional virtual sessions to walk through the testing processes and talk through specific tickets together.
What Could Be Improved
As noted in previous years, the testing team is fairly small and requests can come with little notice and little turnaround time, making it a challenge to complete the testing while balancing other commitments. Any additional notice or time that could be allotted to the testing portion of a release schedule or feature development would be much appreciated. Potential solutions might be include either increasing the size of the sub-team to distribute the work across more people, or to see if members of other TAC/UAC sub-teams would be willing to act as "alternate" testers in the event that one or more members of the testing team are unavailable to turn around the testing in the given timeframe.
A number of Jira tickets require the user to set up a local instance of ArchivesSpace, a skill that many members of the subteam did not have. Perhaps any tickets specifically focused on the program’s code could be a developer to check? Hands-on training for Testing subteam members to do this work would also be of interest.
Leadership Next Year
Lead: Rachel Searcy (TAC)
...