2023-09-06 and 09-11 Testing Team Meeting Agenda

10 min

Welcome New Members and Introductions!

@Austin Munsell /All

Who are you, where do you work, and what area of ArchivesSpace are you least familiar with?

Test

2 min

Can someone take notes?

Does not need to be exhaustive, just things that might be useful looking back that are not already written down.

10 min

Brief Overview of Testing

@Austin Munsell

• Jira Tickets

  • Bugs

  • New Features

  • Major Features (full group testing)

• Full Regression Testing

• Ad Hoc meetings/work sessions will be held with tickets or releases

10 min

Testing Work Plan

@Austin Munsell /All

2023-2024 Testing Workplan

• Major task: we will test things as needed

• Housekeeping: Update the testing protocol as needed

• Longevity: Identify a vice lead for this year to take over in 2024/25

• Communication: With User Docs, identify a method to flag issues that will require updates to the ASpace user documentation

• Other things to add? Please edit, inline comment or email Austin - Revisions due by 9/22 (presenting to TAC and UAC on 9/27)

25 min

JIRA Testing Demo

@Austin Munsell

1. Go to the JIRA ticket from the link in the spreadsheet.

2. Add yourself as a watcher for the issue in JIRA so that you receive any updates (e.g., see additional comments, be notified of status changes). To start watching an issue, click on the eye icon in the upper right corner.

3. Read through the ticket, including the comments, so that you understand the issue.

4. Unless there is a specific server listed for testing, use https://test.archivesspace.org to test the issue (admin/admin for the staff interface login).

5. If the issue appears to be fixed, leave a comment saying as much.

6. If the issue has not been fixed, leave a comment as well, including as much detail about the behavior you are observing. Screenshots and/or an explanation of how to reproduce what you found are very helpful additions.

Testing tips:

• If you have questions about a ticket you’re assigned to test, in addition to bringing it up at a working meeting, you can also email the group or reach out to the other tester(s) assigned to the ticket.

• If asked to test ASpace functionality you’re unfamiliar with or don’t often use, start at the ASpace Help Center.

• Read the ticket comments. They may have additional details, document decision making, etc. between developers, members of DevPri, or even the reporter or other community members who supported the ticket being worked on.

• If you’re on the West coast, be aware that the testing server may go down in the evenings on East coast time.

• May be helpful to create your own record you can test on/with; may make you feel more comfortable to test different tickets.