2025–2026 Testing Work Plan
Purpose
The Testing Sub-team ensures the quality and stability of ArchivesSpace releases through systematic testing, including JIRA ticket verification and full regression testing before major releases.
Term Goals
Onboard New Members & Establish Workflow
Introduce team to tools (Confluence, Google Drive, JIRA); share as needed.
Collect Areas of Expertise for testing assignments
Hold Kickoff meeting (August)
Complete Conditional Statements Project (Carried over from 2024–2025)
Finish updates to functional area testing scripts
Validate and consolidate into Google Drive for future testing cycles
Support ArchivesSpace Release Testing
Conduct JIRA testing as issues become available
Prepare and execute full suite regression testing before major releases
Maintain Communication & Reporting
Provide monthly updates to TAC and UAC as needed
Contribute to quarterly reports for the Governance Board
Prepare end-of-year retrospective
Key Deliverables & Timeline
Month | Activity | Details |
|---|---|---|
July | Onboarding | Send welcome email, share resources |
August | Kickoff Meeting: Review roles, workflows, and priorities | Launch Areas of Expertise poll |
September | Conditional Statements Project Pending: Introduction to new Standards and Testing Archivist |
|
October | Conditional Statements Wrap-Up | Review and finalize scripts; summarize updates in documentation |
November | Quarterly Report | Submit to Governance Board |
December | Release Testing | As needed |
January | Mid-Year Check-In | Review progress, reprioritize if necessary |
February | Release Testing | As needed |
March | Release Testing | As needed |
April | Quarterly Report | Submit to Governance Board |
May | Year-End Retrospective | Identify next term’s Lead/Vice Lead |
Communication Channels
Primary: Email
Documentation: Confluence (general documents, workplans, agendas/meeting minutes, project descriptions)
Testing Resources:
Google Drive: Testing assignments, Conditional Statements scripts, Google Forms
Jira: Tickets, communication with Devs
Roles
Lead (Mary Kidd): Coordinates assignments, facilitates meetings, ensures reporting and documentation
Vice Lead (Stacy Haponik): Assists with facilitation, report-outs, and transitions to Lead role next term
Members: Participate in testing activities, contribute to projects and documentation updates
Standards and Testing Archivist: [Description pending]