Testing Blocker Tickets
- RC-1
External Projects
Hydra (instructions)
Project
Tested by
Success? RC-1
Success RC-2 Notes
ActiveFedora CurationConcerns Hyrax Sufia Plum Valkyrie Avalon 6.0 Islandora
Project
Tested by
Success? RC-1
Success? RC-2 Notes
CLAW API-X
Project
Tested by
Success? RC-1
Success? RC-2 Notes
fcrepo-api-x-integration fcrepo-api-x-demo (Docker) Testing Plan
git clone https://github.com/fcrepo4/fcrepo4 cd fcrepo4 git checkout 4.7.5-RC
Sanity Builds
Project Command Platform Tested By RC 1 Notes fcrepo4 mvn clean install linux
fcrepo4 mvn clean install mac fcrepo4 mvn clean install windows fcrepo-module-auth-rbacl mvn clean install linux fcrepo-module-auth-rbacl mvn clean install mac fcrepo-module-auth-rbacl mvn clean install windows fcrepo-module-auth-xacml mvn clean install linux fcrepo-module-auth-xacml mvn clean install mac fcrepo-module-auth-xacml mvn clean install windows fcrepo-module-auth-webac mvn clean install linux fcrepo-module-auth-webac mvn clean install mac fcrepo-module-auth-webac mvn clean install windows fcrepo-mint mvn clean install linux fcrepo-mint mvn clean install mac fcrepo-mint mvn clean install windows fcrepo-audit mvn clean install linux fcrepo-audit mvn clean install mac fcrepo-audit mvn clean install windows fcrepo-webapp-plus mvn clean install linux fcrepo-webapp-plus mvn clean install mac fcrepo-webapp-plus mvn clean install windows fcrepo-webapp-plus mvn clean install -Pwebac linux fcrepo-webapp-plus mvn clean install -Pwebac mac fcrepo-webapp-plus mvn clean install -Pwebac windows One-Click Run
cd fcrepo-webapp; mvn clean install -Pone-click
Command Platform Tested By RC-1 Notes java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar Linux java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar Mac java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar
Windows Manual Tests
All of the below should take place in the HTML UI and non-vagrant tests should run against fcrepo-webapp-plus.
- Create nested containers
- Create binary resources
- Run fixity on binary
- Update Properties: Perform SPARQL-Update on container
- Update Properties: Perform SPARQL-Update on binary
- Delete container
- Delete binary
- Use transactions
- Create versions
- View versions
- Rollback versions
Database Tests
With Tomcat7 deployment, run above manual tests with alternate backend databases (Configuring JDBC Object Store)
Database Platform Tested by Success RC1? Notes MySQL osx PostgreSQL linux fcr:backup/fcr:restore Functionality
These tests are designed to ensure the proper function of the 'fcr:backup/fcr:restore' features by testing them against various Fedora configurations. The validity of the 'restore' can only be determined by crawling the repository and verifying the successful retrieval of the repository's content.
If the anticipated Fedora release is not backwards compatible with the previous version of Fedora, then the "From Fedora Version" should be the previous version. Otherwise, it is sufficient to test the fcr:backup/fcr:restore functionality using the same version.
See: RESTful HTTP API - Backup and Restore
# Backup curl -X POST localhost:8080/rest/fcr:backup # Restore curl -X POST -d "/path/to/backup/directory" localhost:8080/rest/fcr:restore
Resources
- These python scripts - fcrepo-testing - can be used to load RDF content and binary content to a Fedora repository and verify the integrity of the loaded resources. Output from the load process can be used to verify the integrity of a 'restored' repository. See the README for more info.
- This script can be used to walk your repository, failing if a non-success response is encountered.
Tested by
Platform
Container
(Tomcat/Jetty)
Database
Backend
From Fedora
VersionTo Fedora
VersionNumber of
RDF Resources
Number of
Binaries
Size of Backup (du -h .)
Success?
Notes
Linux Jetty File-simple 4.7.5 4.7.5 100 NB: "Success" is measured not by receiving a "204 No Content" message after the 'fcr:restore' command, but by performing a GET on every resource in the repository and receiving "200 OK" messages.
Vagrant Tests
vagrant destroy vagrant up
Test steps Tested By Success RC1? Notes FEDORA_AUTH=true
FEDORA_AUDIT=falseFEDORA_AUTH=false
FEDORA_AUDIT=falseFEDORA_AUTH=true
FEDORA_AUDIT=trueFEDORA_AUTH=false
FEDORA_AUDIT=trueManual Tests
Same as above, plus:
- Verify audit events are in triplestore
- Verify resources are in triplestore
- Verify resources are in Solr
- Verify authorization works for the two auth-enabled configurations
- Verify reindexing to triplestore works
Backwards Compatibility Tests
- Start 4.7.4 one-click
- Load sample datasets via /fcr:restore
- Run test scripts on 4.7.4
- Stop 4.7.4
- Start RC one-click
- Run test scripts on RC
- ReStart RC
- Run test scripts on RC
Tested by Success RC2 Notes Resources
[1] Testing scripts