Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »




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.


  • 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
    • As a secondary benefit, it would be great if these plans can work as a model for in-house testing of your own upgrades.
    • It should be very clear what the reference installation on entails

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

Different people's own test plans (examples)

Virginia Tech, VTechWorks -

  • LIKE
    • Bram: column with "expected results".
    • ...

Georgetown University Institutional Repository -

  • LIKE
    • Bram: Section column to group tests together
    • ...


Atmire -

  • LIKE
    • Categorization of what the different types of feedback can be
    • Columns for different servers
    • Mix of things that can be tested in the UI & technical things that can only be verified by an admin.


Edinburgh - 

  • LIKE

Mandatory fields (per test)


Structure of the test spreadsheets



Requirements for installation

Integrations with external systems

Following integrations may not be enabled out of the box. They need to be configured to ensure they are "up and running" on

  • DOI
  • Google Analytics
  • Creative Commons (licensing)
  • Sherpa Romeo Lookup
  • LDAP or other custom authentication methods
    • Many people use this feature but I can't see how we can enable this on without also putting up an entire directory infrastructure.

Specific credentials

  • Admin email inbox: specific testers should have access to the email inbox that SHOULD receive entries in the repository feedback from, the "Request a copy" requests, ...
  • Google Analytics account

Checklist for features that should be enabled

  • Workflow: Basic workflow or XML workflow ??? Only one of the two can be enabled.
  • PDF cover page?
  • Versioning
  • Collection strength should be shown
  • Legacy stats ???? (Bram: I'm not in favor of still showing these or recommending use of them to anyone, but some people still seem to use them)
  • Thumbnail generation (filter media execution and potential XPDF installation)
  • outgoing email

DRAFT of our procedures that we want to add to the official testathon page

Unless specified otherwise, the credentials that should be used for the tests are the ones listed on the and /jspui homepages. 

Testathon page: DSpace Release 6.0 Testathon Page

  • No labels