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

Compare with Current View Page History

« Previous Version 29 Next »

Testing Blocker Tickets

  • ...

External Projects

Hydra

Project

Tested by

Success? RC-1

Notes

ActiveFedora
CurationConcerns

(tick)


Hyrax

(tick)

(tick)


Plum(tick)
 
Sufia(tick)
 

Islandora

 Project

Tested by

Success? RC-1

Notes

CLAW(tick)#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

ProjectCommandPlatformTested bySuccess?Notes
fcrepo4mvn clean install

linux

(tick)  
fcrepo4mvn clean install mac Jared Whiklo (tick)  
fcrepo4mvn clean installwindowsAaron Birkland (tick)  
fcrepo-module-auth-rbaclmvn clean installlinux(tick)  
fcrepo-module-auth-rbaclmvn clean install mac Jared Whiklo(tick)  
fcrepo-module-auth-rbaclmvn clean installwindows(tick)  
fcrepo-module-auth-xacmlmvn clean install linux(tick)  
fcrepo-module-auth-xacmlmvn clean install macJared Whiklo (tick)  
fcrepo-module-auth-xacmlmvn clean installwindows(tick)  
fcrepo-module-auth-webacmvn clean install linux(tick)  
fcrepo-module-auth-webacmvn clean install mac(tick)  
fcrepo-module-auth-webacmvn clean installwindows(tick)  
fcrepo-mintmvn clean install linux(tick)  
fcrepo-mintmvn clean install mac(tick)  
fcrepo-mintmvn clean installwindowsAaron Birkland (tick)  
fcrepo-auditmvn clean install linux(tick)  
fcrepo-auditmvn clean install mac(tick)  
fcrepo-auditmvn clean installwindows(tick) 
fcrepo-webapp-plusmvn clean install linux(tick)  
fcrepo-webapp-plusmvn clean install mac(tick)  
fcrepo-webapp-plusmvn clean install windows(tick) 
fcrepo-webapp-plusmvn clean install -Pwebac linux(tick) 

 

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

 

fcrepo-webapp-plusmvn clean install -Pauditmac (tick) 
fcrepo-webapp-plusmvn clean install -Pauditwindows (tick) 
fcrepo-webapp-plusmvn clean install -P\!webac,\!auditlinux(tick)  
fcrepo-webapp-plusmvn clean install -P\!webac,\!auditmac (tick) 
fcrepo-webapp-plusmvn clean install -P\!webac,\!auditwindows (tick) 

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)
(tick)
 
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jarMac Youn Noh      (tick)Namespace prefix bindings in transactions that are rolled back persist.

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

Windows(tick) 

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   

 

PostgreSQLMacOSX 10.12.5
PostgreSQL 9.4.5
Esmé Cowles(tick)

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

FEDORA_AUTH=true
FEDORA_AUDIT=true

(tick)

(tick)

 

FEDORA_AUTH=false
FEDORA_AUDIT=true

(tick)

(tick)

 

FEDORA_AUTH=true
FEDORA_AUDIT=false

(tick)

(tick)

 

FEDORA_AUTH=false
FEDORA_AUDIT=false

(tick)

(tick)

 

Manual Tests

Same as above, plus:

  1. Verify audit events are in triplestore (tick)
  2. Verify resources are in triplestore (tick) (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)
  3. Verify resources are in Solr (tick)
  4. Verify authorization works for the two auth-enabled configurations (tick)
  5. Verify reindexing to triplestore works (tick) (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

  1. 4.7.2
    1. Start 4.7.0 with a new data directory
    2. Create a resource with SKOS namespace
      1. 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/

    3. Stop 4.7.0 and start 4.7.2 with the same data directory
    4. View the record from 1.b. ??
      1. Note: this did not reproduce the error for me
  2. 4.7.3
    1. Repeat 1., but deploying 4.7.3 and verifying that the error does not occur

[1] Testing scripts

[2] Fedora 4 Release Test Suite

  • No labels