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

Compare with Current View Page History

« Previous Version 14 Next »

Testing Blocker Tickets

External Projects

Hydra (instructions)

Project

Tested by

Success? RC-1

Notes

ActiveFedora




CurationConcerns




Hyrax


Sufia


Plum(tick)
 
ValkyrieEsmé Cowles(tick)

Islandora

 Project

Tested by

Success? RC-1

Notes

CLAW




Testing Plan

git clone https://github.com/fcrepo4/fcrepo4
cd fcrepo4
git checkout 4.7.4-RC

Sanity Builds

ProjectCommandPlatformTested bySuccess?Notes
fcrepo4mvn clean install

linux

(tick)  
fcrepo4mvn clean install mac Jared Whiklo  (tick) 
fcrepo4mvn clean installwindows   
fcrepo-module-auth-rbaclmvn clean installlinux

 

  
fcrepo-module-auth-rbaclmvn clean install mac(tick)  
fcrepo-module-auth-rbaclmvn clean installwindows   
fcrepo-module-auth-xacmlmvn clean install linux

 

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

 

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

 

  
fcrepo-auditmvn clean install mac(tick)  
fcrepo-auditmvn clean installwindows   
fcrepo-webapp-plusmvn clean install linux

 

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

 

fcrepo-webapp-plusmvn clean install -Pwebacmac(tick)  
fcrepo-webapp-plusmvn clean install -Pwebacwindows   

One-Click Run

cd fcrepo-webapp; mvn clean install -Pone-click
CommandPlatform Tested bySuccess? Notes
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jarLinux(tick)  
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jarMac Danny Bernstein(tick)  

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.

  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?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
Version

To Fedora 
Version

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 stepsTested bySuccess? - RC2Notes

FEDORA_AUTH=true
FEDORA_AUDIT=false

(tick)  

FEDORA_AUTH=false
FEDORA_AUDIT=false

(tick) 

 

FEDORA_AUTH=true
FEDORA_AUDIT=true

(tick)

FEDORA_AUTH=false
FEDORA_AUDIT=true

(tick)

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

[1] Testing scripts

[2] Fedora 4 Release Test Suite

  • No labels