Introduction
This page was created after the DCAT Meeting September 2015, where a working group was formed to prepare the test plans for the DSpace 6 Testathon.
Objectives
- Create two plans, one for XMLUI, one for JSPUI
- Create these plans as collaborative spreadsheets (Google Docs)
- Group the different tests per user persona/access level
- Anonymous - Non-authenticated, anonymous users
- Submitter - Authenticated user with submission rights
- Collection Admin - Authenticated user with collection administration rights
- Admin - Authenticated user with admin rights
- Create plans to be used on demo.dspace.org
- As a secondary benefit, it would be great if these plans can work as a model for in-house testing of your own upgrades.
Out of scope
- Specific work on DSpace documentation
- This will be treated in parallel, related to each new feature for which documentation needs to be reviewed
- Tests for the other DSpace webapps
- OAI-PMH
- REST
- SWORD
- LNI
- Performance and Load tests
Official drafts
JSPUI Test plan: TODO
XMLUI Test plan: TODO
Different people's own test plans (examples)
Virginia Tech, VTechWorks - https://docs.google.com/spreadsheets/d/1_-20Y06C8dP2VzWxaSBbMnXgvuBOQoc3D0chJGRmyGg/edit?usp=sharing
- LIKE
- Bram: column with "expected results".
- DISLIKE / NOT APPLICABLE
- ...
Georgetown University Institutional Repository - https://docs.google.com/spreadsheets/d/1QkasjcwhhiAj4HXIDFDeX7TFEocwnqsZGnmDTHNmnCs/edit?usp=sharing
- LIKE
- Bram: Section column to group tests together
- DISLIKE / NOT APPLICABLE
- ...
- LIKE
- Categorization of what the different types of feedback can be
- DISLIKE/NOT APPLICABLE HERE
- Columns for different servers
- Mix of things that can be tested in the UI & technical things that can only be verified by an admin.
- LIKE
- DISLIKE / NOT APPLICABLE HERE
Mandatory fields (per test)
...
Structure of the test spreadsheets
...
DRAFT of our procedures that we want to add to the official testathon page
Testathon page: DSpace Release 6.0 Testathon Page
