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 27 Next »

Testing Blocker Tickets

External Projects

Hydra (instructions)


Tested by

Success? RC-1

Success RC-2


ActiveFedoraEsmé Cowles(tick)




Avalon 6.0



Tested by

Success? RC-1

Success? RC-2





Tested by

Success? RC-1

Success? RC-2



fcrepo-api-x-demo (Docker)

Testing Plan

git clone
cd fcrepo4
git checkout 4.7.5-RC

Sanity Builds

ProjectCommandPlatformTested ByRC 1Notes
fcrepo4mvn clean install


fcrepo4mvn clean install mac Joshua Westgard(tick)Frequent warning: "Unable to update victims database! Your CVE records might be out of date."
fcrepo4mvn clean installwindowsBen Pennell(error) 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).
fcrepo-module-auth-rbaclmvn clean installlinux(tick) 
fcrepo-module-auth-rbaclmvn clean install mac


Frequent warning: "Unable to update victims database! Your CVE records might be out of date."

fcrepo-module-auth-rbaclmvn clean installwindows

fcrepo-module-auth-xacmlmvn clean install linux(tick) 
fcrepo-module-auth-xacmlmvn clean install mac???No 4.7.5-RC branch or tag
fcrepo-module-auth-xacmlmvn clean installwindows

fcrepo-module-auth-webacmvn clean install linux(tick) 
fcrepo-module-auth-webacmvn clean install mac(tick)

Frequent warning: "Unable to update victims database! Your CVE records might be out of date."

fcrepo-module-auth-webacmvn clean installwindows

fcrepo-mintmvn clean install linux(tick) 
fcrepo-mintmvn clean install mac(tick)

Frequent warning: "Unable to update victims database! Your CVE records might be out of date."

fcrepo-mintmvn clean installwindows

fcrepo-auditmvn clean install linux(tick) 
fcrepo-auditmvn clean install mac(tick)Frequent warning: "Unable to update victims database! Your CVE records might be out of date."
fcrepo-auditmvn clean installwindows

fcrepo-webapp-plusmvn clean install linux(tick) 
fcrepo-webapp-plusmvn clean install mac(tick)Frequent warning: "Unable to update victims database! Your CVE records might be out of date."
fcrepo-webapp-plusmvn clean install windows

fcrepo-webapp-plusmvn clean install -Pwebac linux(tick)


fcrepo-webapp-plusmvn clean install -Pwebacmac(tick)Frequent warning: "Unable to update victims database! Your CVE records might be out of date."
fcrepo-webapp-plusmvn clean install -Pwebacwindows


Note (18 January 2018): The victims database warnings are due to the site currently returning a 503 error. Jared Whiklo has reported this issue upstream:

One-Click Run

cd fcrepo-webapp; mvn clean install -Pone-click
CommandPlatformTested ByRC-1Notes
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jarLinux(tick) 
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jarMacJoshua Westgard(tick) 

java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar



Manual Tests

All of the below should take place in the HTML UI and non-vagrant tests should run against fcrepo-webapp-plus.

  1. Create nested containers
  2. Create binary resources
  3. Run fixity on binary
  4. Update Properties:  Perform SPARQL-Update on container
  5. Update Properties:  Perform SPARQL-Update on binary
  6. Delete container
  7. Delete binary
  8. Use transactions
  9. Create versions
  10. View versions
  11. Rollback versions

Database Tests

With Tomcat7 deployment, run above manual tests with alternate backend databases (Configuring JDBC Object Store)

DatabasePlatformTested bySuccess RC1?Notes
MySQL osx



Danny Bernstein: (error)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.

PostgreSQLosxJoshua Westgardconfig successful; testing in progress
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


  • 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






From Fedora

To Fedora 

Number of

RDF Resources

Number of


Size of Backup (du -h .)




LinuxTomcatPostgres4. G(tick)Performed a GET test on all resources in 4.7.5 before /fcr:restore, thereby mimicking an 'in place upgrade.'  All succeeded.
In progress

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 stepsTested BySuccess RC1?Notes







Manual Tests

Same as above, plus:

  1. Verify audit events are in triplestore
  2. Verify resources are in triplestore
  3. Verify resources are in Solr
  4. Verify authorization works for the two auth-enabled configurations
  5. Verify reindexing to triplestore works

Backwards Compatibility Tests

  1. Start 4.7.4 one-click
  2. Load sample datasets via /fcr:restore
  3. Run test scripts on 4.7.4
  4. Stop 4.7.4
  5. Start RC one-click
  6. Run test scripts on RC
  7. ReStart RC
  8. Run test scripts on RC
Tested bySuccess RC2Notes
(tick)Did not run camel_toolbox_tests or authz_tests.


[1] Testing scripts

[2] Fedora 4 Release Test Suite

  • No labels