Quality Assurance Practices
Table of Contents
About QA Practices
This page outlines QA practices for the CollectionSpace software development.
For releases x through 8.0, quality assurance testing was coordinated by the CollectionSpace Program Manager with community volunteers. With the 8.1 release, the CollectionSpace program utilized consultation services to complete testing. Historical information about testing remains on the previous wiki.
Current and Past Testing Plans
New Feature Tests
Test plans for new features include a combination of tests based on type of feature and plans specific to a given release. See New Feature Tests for general test plans that apply to all releases.
Regression Testing
Regression testing is a technique used to ensure that recent code changes, including bug fixes or new features, have not negatively impacted existing functionality.
Test Plan Template
When creating a new test plan, please duplicate the Test Plan Template. This page outlines the descriptions and provides formatting for test plans. NOTE: This template was introduced for the 8.3 release and beyond. Past test plans did not follow this format.
Data Layer QA Process
A separate “data layer QA” process was introduced around the time the CollectionSpace CSV Importer was built (early-to-mid 2021). This process is documented here. This process is intended to:
Catch issues in field naming/namespacing that introduce inconsistency into the overall data model
Catch issues that will cause problems in the ingest stack. In some cases (such as duplicate field name added in a record type), the issue can be fixed pre-release. In other cases (such as introduction of a new data structure/pattern), this gives us time to make the necessary changes in the ingest stack prior to release.
Catch minor issues such as typos in field names or labels
Catch issues related to the Core Profile implementation.