Skip to end of metadata
Go to start of metadata

Testing the User Interface (UI)

Currently, the UI layer is only tested manually. It is planned that a suite of automatted acceptance testing of the UI is to be set up when the time allows for it. But even once this is done, manual testing of the UI is very important. Testing manually allows finding visual bugs on the page, and is obviously as close to the end user experince as it gets. Furthermore, since the UI uses the backend, all the three layers of collectionspace will be tested when doing UI tests.

A set of test plans that attempts to cover the entire CollectionSpace program has been written. These can be found on the page: QA Test plans - Listing. In periods of QA, immediately preceeding a release, all these tests are run on the supported environments by the entire CollectionSpace team. During development phases, a subset of these might also be run, as to test newly implemented functionality as well as to ensure that new commits have not broken any previous functionality.

Get Involved

There are several ways to get involved in collectionspace, as described on the Get Involved page. A good way to get involved for the less technical minded user, or for a developer: as a way to get familiar with CollectionSpace before starting to contribute code, is to particpate in the testing.

There are multiple ways to get involved in the testing of CollectionSpace:

  • Testing in periods of QA: In a period before release, the entire CollectionSpace team stops coding and focus solely on testing. The testing in these periods is based on the testplans (QA Test plans - Listing). This is a big task, and any help in these periods is highly appreciated. A schedule can be found here: CollectionSpace Project Roadmap - Detailed. For help on how to follow the test plans, reader is referred to Guidelines for following a test plan.
  • Ad hoc testing: Although it is attempted to cover every usecase in the testplans, this might not always be possible. Ad hoc testing is when we bang on the application with no particular order or script to find oddities that might be hidden from scripted/planned testing. This sort of testing is particularly appropriate for end users to participate in, since developers might be blinded by their familiarity with the code and intended usage.
  • Test plan writing: As the development of CollectionSpace is very rapid, there is a constant work in keeping the exisiting test-plans up to date, as well as to add new plans testing the new functionality. Information on how to write test plans can be found here: General Guidelines for QA Test Writing for the UI

Supported Environment

The page Supported Environment could not be found.

JIRAs, bug finding and bug filing

For keeping track of bugs, CollectionSpace uses Atlassians JIRA tools. This is located at You need to sign up for an account to be able to report bugs.

To sign up for a JIRA account, follow the guide on this page: JIRA sign up instructions

Guidelines on how to report a bug are described on this page: Guidelines for Filing a JIRA Bug Report. This is a highly recommended read.

  • No labels