Testing Blocker Tickets
- ...
External Projects
Hydra
Project | Tested by | Success? RC-1 | Notes |
---|---|---|---|
ActiveFedora | |||
CurationConcerns | |||
Hyrax | |||
Plum | |||
Sufia |
Islandora
Project | Tested by | Success? RC-1 | Notes |
---|---|---|---|
CLAW | #IslandoraCon demo works fine with 4.7.3-RC1 |
Testing Plan
git clone https://github.com/fcrepo4/fcrepo4 cd fcrepo4 git checkout <version>-RC
Sanity Builds
Project | Command | Platform | Tested by | Success? | Notes |
---|---|---|---|---|---|
fcrepo4 | mvn clean install | linux | |||
fcrepo4 | mvn clean install | mac | Jared Whiklo | ||
fcrepo4 | mvn clean install | windows | Aaron Birkland | ||
fcrepo-module-auth-rbacl | mvn clean install | linux | |||
fcrepo-module-auth-rbacl | mvn clean install | mac | Jared Whiklo | ||
fcrepo-module-auth-rbacl | mvn clean install | windows | |||
fcrepo-module-auth-xacml | mvn clean install | linux | |||
fcrepo-module-auth-xacml | mvn clean install | mac | Jared Whiklo | ||
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 | Aaron Birkland | ||
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 | |||
fcrepo-webapp-plus | mvn clean install -Paudit | linux |
| ||
fcrepo-webapp-plus | mvn clean install -Paudit | mac | | ||
fcrepo-webapp-plus | mvn clean install -Paudit | windows | | ||
fcrepo-webapp-plus | mvn clean install -P\!webac,\!audit | linux | |||
fcrepo-webapp-plus | mvn clean install -P\!webac,\!audit | mac | | ||
fcrepo-webapp-plus | mvn clean install -P\!webac,\!audit | windows | |
One-Click Run
cd fcrepo-webapp; mvn clean install -Pone-click
Command | Platform | Tested by | Success? | Notes |
---|---|---|---|---|
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar | Linux | |||
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar | Mac | Youn Noh | Namespace prefix bindings in transactions that are rolled back persist. | |
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? | Notes |
---|---|---|---|---|
MySQL | ||||
PostgreSQL |
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 | To Fedora | Number of RDF Resources | Number of Binaries | Size of Backup (du -h .) | Success? | Notes |
---|---|---|---|---|---|---|---|---|---|---|
Linux |
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? | Notes |
---|---|---|---|
FEDORA_AUTH=true | |||
FEDORA_AUTH=false |
| ||
FEDORA_AUTH=true | |||
FEDORA_AUTH=false |
Manual Tests
Same as above, plus:
- Verify audit events are in triplestore
- Verify resources are in triplestore (Note: indexing works very poorly when using the testing scripts because rapidly adding and then removing items causes the message queue to get very backed up)
- Verify resources are in Solr
- Verify authorization works for the two auth-enabled configurations
- Verify reindexing to triplestore works (tested by looking in fuseki after each step: adding a resource, adding a dc:title, removing dc:title, deleting resource. Did not test the camel separate reindexing feature.)
4.7.0 - 4.7.2 Upgrade Testing
Tests to verify if 4.7.3 resolves errors seen with upgrading from 4.7.0 to 4.7.2
- 4.7.2
- Start 4.7.0 with a new data directory
- Create a resource with SKOS namespace
curl -X POST -d "<> a <http://www.w3.org/2004/02/skos/core#Concept>; <http://www.w3.org/2004/02/skos/core#prefLabel> 'foo' ." -H "Content-type: text/turtle" -D - http://localhost:8080/rest/
- Stop 4.7.0 and start 4.7.2 with the same data directory
- View the record from 1.b. ??
- Note: this did not reproduce the error for me
- 4.7.3
- Repeat 1., but deploying 4.7.3 and verifying that the error does not occur
[1] Testing scripts