...
Each issue is assigned randomly to two members of the testing team. The testers then review the issue to understand the feature request, change or fix and then test - typically in the sandbox at test.archivesspace.org. If the test is successful, then each tester will add a comment to the issue stating that the testing was successful. If the test is not successful, each tester will comment on the issue with details about how the test failed. They should include screenshots if applicable and as much information as needed so that the developers have a clear picture of the problem.
Lifecycle of a JIRA ticket:
Full Suite Testing
Prior to a new release, each main section of the application is tested to ensure that any changes to ArchivesSpace do not break existing workflows. These main sections typically represent the top level areas of the application - Resources, Accessions, Archival Objects, Reports, User Management, etc. Again, each section is randomly assigned to two testers. A worksheet is provided to each tester so that they can track the results of their testing. Each tester completes the portions of the worksheet assigned to them and indicates whether the tests were successful or not. If a specific test is not successful, the tester should provide details (including screenshots if applicable) detailing how the test failed.
...