Testing Blocker Tickets
- RC-1
External Projects
Hydra (instructions)
Project | Tested by | Success? RC-1 | Success RC-2 | Notes |
---|---|---|---|---|
ActiveFedora | Esmé Cowles | |||
Hyrax | ||||
Sufia | ||||
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 | RC 2 | Notes |
---|---|---|---|---|---|---|
fcrepo4 | mvn clean install | linux | ||||
fcrepo4 | mvn clean install | mac | Joshua Westgard | Frequent warning: "Unable to update victims database! Your CVE records might be out of date." | ||
fcrepo4 | mvn clean install | windows | I wasn't able to perform a sanity build in Windows 10 due to some integration tests in fcrepo-kernel-modeshape failing. A few of them were failing because the last modified date for binaries was not updating all of the time (tests were flapping). Danny Bernstein: NB - apparently this has been an ongoing issue. Apparently Windows 10 on hyper-v works, but is failing/flapping on direct windows install. Aaron Birkland and Yinlin Chen worked on resolving this a while back but did not crack it. | |||
fcrepo-module-auth-rbacl | mvn clean install | linux | ||||
fcrepo-module-auth-rbacl | mvn clean install | mac | Frequent warning: "Unable to update victims database! Your CVE records might be out of date." | |||
fcrepo-module-auth-rbacl | mvn clean install | windows | Aaron Birkland | |||
fcrepo-module-auth-xacml | mvn clean install | linux | ||||
fcrepo-module-auth-xacml | mvn clean install | mac | ??? | No 4.7.5-RC branch or tag | ||
fcrepo-module-auth-xacml | mvn clean install | windows | ||||
fcrepo-module-auth-webac | mvn clean install | linux | ||||
fcrepo-module-auth-webac | mvn clean install | mac | Frequent warning: "Unable to update victims database! Your CVE records might be out of date." | |||
fcrepo-module-auth-webac | mvn clean install | windows | Aaron Birkland | |||
fcrepo-mint | mvn clean install | linux | ||||
fcrepo-mint | mvn clean install | mac | Frequent warning: "Unable to update victims database! Your CVE records might be out of date." | |||
fcrepo-mint | mvn clean install | windows | Aaron Birkland | |||
fcrepo-audit | mvn clean install | linux | ||||
fcrepo-audit | mvn clean install | mac | Frequent warning: "Unable to update victims database! Your CVE records might be out of date." | |||
fcrepo-audit | mvn clean install | windows | Aaron Birkland | |||
fcrepo-webapp-plus | mvn clean install | linux | ||||
fcrepo-webapp-plus | mvn clean install | mac | Frequent warning: "Unable to update victims database! Your CVE records might be out of date." | |||
fcrepo-webapp-plus | mvn clean install | windows | Aaron Birkland | |||
fcrepo-webapp-plus | mvn clean install -Pwebac | linux |
| |||
fcrepo-webapp-plus | mvn clean install -Pwebac | mac | Frequent warning: "Unable to update victims database! Your CVE records might be out of date." | |||
fcrepo-webapp-plus | mvn clean install -Pwebac | windows | Aaron Birkland |
Note (18 January 2018): The victims database warnings are due to the victi.ms site currently returning a 503 error. Jared Whiklo has reported this issue upstream: https://github.com/victims/victims-web/issues/155
One-Click Run
cd fcrepo-webapp; mvn clean install -Pone-click
Command | Platform | Tested By | RC-1 | RC-2 | Notes |
---|---|---|---|---|---|
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar | Linux | ||||
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar | Mac | Joshua Westgard | |||
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? | Success RC2? | Notes |
---|---|---|---|---|---|
MySQL | osx | Danny Bernstein: Restoring v1 after creating v2 does not seem to work: Steps to reproduce: 1. Create a binary with fileA.jpg 2. Create version v1. 3. Update binary with fileB.jpg 4. Create version v2. 5. Click on versions link and click on v1 link. 6. Click "Revert to this Version" 7. Return to binary resource metadata page. Notice the file associated with the version fileB.jpg rather than the expected fileA.jpg. It does not appear that the version was reverted. Joshua Westgard: Hey Danny Bernstein, when I tested the versioning I was just making changes to metadata not binaries and didn't notice any problems; after seeing your note, however, I tried with a binary and did notice that the browser cached the previous version, so after restoring it was still displaying the previous data, but upon refreshing the resource page the restored version was visible as expected. Any chance this is the same problem you were seeing? Joshua Westgard: could be, though I thought I did a hard refresh. I'll try it again to conf hirm. Joshua Westgard: I must not have done a hard refresh. So yes after a hard refresh it worked. I wonder if it should be a logged as a bug nevertheless. Ideally any refresh would not be required at all. A Command-R refresh doesn't refresh the page. Only Command-Shift-R. It seems like it could be a source of confusion. Perhaps a JIRA is warranted. | |||
PostgreSQL | osx | Joshua Westgard | config successful; testing in progress | ||
PostgreSQL | linux | Kevin Ford | Tests were performed against fcrepo-webapp-4.7.5-RC-1 not fcrepo-webapp-plus-4.7.5-RC-1. | ||
MySQL5.6 | linux | Kevin Ford | Tests were performed against fcrepo-webapp-4.7.5-RC-1 not fcrepo-webapp-plus-4.7.5-RC-1. | ||
PostgreSQL | linux | Kevin Ford | Tests were performed against fcrepo-webapp-plus-4.7.5-RC-1. | ||
MySQL5.6 | linux | Kevin Ford | Tests were performed against fcrepo-webapp-plus-4.7.5-RC-1. |
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 RC1? | Success RC2? | Notes |
---|---|---|---|---|---|---|---|---|---|---|---|
Linux | Jetty | File-simple | 4.7.5 | 4.7.5 | 100 | ||||||
Linux | Tomcat | Postgres | 4.7.1 | 4.7.5-RC-1 | 6400 | 6400 | 6.7 G | Performed a GET test on all resources in 4.7.5 before /fcr:restore, thereby mimicking an 'in place upgrade.' All succeeded. | |||
Linux | Tomcat | Postgres | 4.7.3 | 4.7.5-RC-1 | 6400 | 6400 | 6.7 G | Performed a GET test on all resources in 4.7.5 before /fcr:restore, thereby mimicking an 'in place upgrade.' All succeeded. | |||
Linux | Tomcat | Postgres | 4.7.4 | 4.7.5-RC-1 | 6400 | 6400 | 6.7 G | Performed a GET test on all resources in 4.7.5 before /fcr:restore, thereby mimicking an 'in place upgrade.' All succeeded. | |||
Linux | Tomcat | Mysql | 4.7.4 | 4.7.5-RC-1 | 79456 | 11969 | 96G | Performed an fcr:export from 4.7.4. Performed an fcr:import to 4.7.5-RC-1. Performed a reindex using camel (to walk all RDF resources). I did not test every binary. | |||
Linux | Tomcat | Mysql 5.6 | 4.7.5 | 4.7.5-RC-1 | 6400 | 6400 | 6.7 G | ||||
Linux | Tomcat | Postgres | 4.7.5 | 4.7.5-RC-1 | 6400 | 6400 | 6.7 G | Back up actually created from a mysql backend repo. |
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 RC2? | 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
- 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 RC1 | Success RC2 | Notes |
---|---|---|---|
Did not run camel_toolbox_tests or authz_tests. | |||
Resources
[1] Testing scripts