2022-09-13 Testing minutes

Attendees: Cory Nimer, Austin Munsell, Suzanne Reller, Sarit Hand, Rachel Searcy, Elizabeth Caringola

Welcome (Cory Nimer)

Old Business: 

New Business: 

• 2022-2023 Work Plan

  • 2021-2022 plan: 

The testing team will perform regression testing for any releases as they become available and will test specific JIRA issues as assigned. We will also review and update the Testing Process - 2016.

New members will be onboarded with guided testing for the first JIRA assignments and first full regression tests. We also plan to meet quarterly (or as needed) to review testing procedures for JIRA & full regression testing.

• UAC has asked for greater engagement between subteams or with the ArchivesSpace community as part of this year's work plan

  • Could be working together with another team on documentation gaps, or reaching out to the community, but generally hoping for collaboration and looking for places where team work intersects

  • Don't need to have a clear plan, but need to include some language about seeking opportunities for collaboration

  • Once work plans are submitted, council chairs will be reviewing to suggest places for further collaboration

  • One area that could be focused on is documentation--making sure that information about the feature is included in user or technical docs

    • Could see about collaborating with doc team members during review of JIRA tickets to clarify when documentation updates are needed (could just be done in the ticket itself, if Doc Team were watchers on the tickets already)

  • Need to be aware that testing can come with a quick turn-around, need to be sure that whatever we establish is sustainable--maybe not overly ambitious

• Work plan draft: 

The testing team will perform regression testing for any releases as they become available and will test specific JIRA issues as assigned. We will also review and update the Testing Process - 2016. This review will explore ways of integrating the User Documentation Team, Technical Documentation Team, or other groups into the testing process.

New members will be onboarded regarding procedures at the beginning of the term. Team will meet as needed to revise procedures, and will hold group meetings for testing during JIRA and full regression testing.

• Testing procedures

  • Assignments

    • Assignments are made as new releases approach, and can include both specific tickets and regression testing of the whole application

    • Releases are generally scheduled, but there these can shift making it difficult to plan for exactly

    • Assignments are made with double coverage, and we also have a larger membership than other teams to be sure that things get tested

    • Could also look into alternative testers from other teams, or reaching out to community members if needed

      • Perhaps the team could be most focused on JIRA tickets, while others could be invited to participate in the regression testing

      • Developing a pool could be an opportunity for collaboration

    • Tickets are at times not clear--may need to ask Christine for clarification, but also may want to work with Dev Pri to clarify what work was approved

      • Summaries of Dev Pri discussion is recorded in their minutes (https://archivesspace.atlassian.net/wiki/spaces/AC/pages/3140452353 ) and may not make it into the JIRA ticket

  • Local instances

    • Christine mentioned that they have a developer that can set up and test these tickets if needed

    • Some members interested in learning about process, but are not currently in a position to do that sort of testing

      • Could we set up a training with developers, perhaps later in the term

  • Meet-ups

    • Meetings around release of tickets, or during regression testing, works best

    • This meeting provides general onboarding for procedures, additional training can be provided during group meetings

    • Could look at ways of streamlining assignment management and submission -- also include a link to the Google Drive in the Confluence page

      • Need to update permissions in Google Drive, if possible

Action Items: 

• Finalize work plan (Cory and Austin)

• Distribute JIRA testing assignments (Cory and Austin)

• Schedule testing collaboration meeting in two weeks (Cory)

• Check with Christine about establishing regular JIRA testing schedule, and roadmap for releases this term; also confirm Scrum meeting schedule and attendance (Cory)

• Update Google Drive permissions

Next Meeting: 

• TBD based on Doodle results