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

Compare with Current View Page History

« Previous Version 33 Next »

Testing Blocker Tickets

  • ...

External Projects

Samvera

Project

Tested by

Success?
RC-1

Success?
RC-2

Success?
RC-3

Notes

ActiveFedora






CurationConcerns






Hyrax




Valkyrie

(tick)




Sufia






Islandora

 Project

Tested by

Success? 
RC-1

Success?
RC-2

Success?
RC-3

Notes

Islandora 8(tick)(tick)
Confirmed https://jira.duraspace.org/projects/FCREPO/issues/FCREPO-3015 is fixed in RC-2

Testing Plan

git clone https://github.com/fcrepo4/fcrepo4
cd fcrepo4
git checkout <version>-RC

Sanity Builds

Scripts

https://github.com/awoods/fcrepo-build-scripts

ProjectCommandPlatformTested bySuccess? RC-1Success?
RC-2

Success?
RC-3

Notes
fcrepo4mvn clean install

linux

(tick)(tick)
(tick)
fcrepo4mvn clean install mac (tick)(tick)
fcrepo4mvn clean installwindowsAaron Birkland

(tick)

One-Click Run

cd fcrepo-webapp; mvn clean install -Pone-click
CommandPlatform Tested bySuccess?
RC-1
Success?
RC-2

Success?
RC-3

Notes
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jarLinux(tick)(tick)
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jarMac(tick)(tick) (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.

  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
PlatformTested bySuccess?
RC-1
Success?
RC-2

Success?
RC-3

Notes
OS X(tick)(tick)

Linux (Ubuntu)

(tick)

Database Tests

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

DatabasePlatformTested bySuccess?
RC-1
Success?
RC-2

Success?
RC-3

Notes
MySQLUbuntu(tick)(tick)
Tomcat 8
PostgreSQLUbuntu(tick)(tick)
Tomcat 8

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?
RC-1

Success?
RC-2

Success?
RC-3

Notes                  

LinuxjettyFile-simple5.1.0-RC25.1.0-RC2

13061


3.7m
(tick)
Run on ubuntu xenial. Scripts difficult to use in centos7
OSX










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
Tested bySuccess?
RC-1
Success?
RC-2

Success?
RC-3

Notes
(tick)(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 reindexing to triplestore works
Tested bySuccess?
RC-1
Success?
RC-2

Success?
RC-3

Notes

(tick)






Backwards Compatibility Tests

  1. Start 5.0.0 one-click
  2. Load sample datasets via /fcr:restore
  3. Run test scripts on 5.0.0
  4. Stop 5.0.0
  5. Start RC one-click
  6. Run test scripts on RC
  7. ReStart RC
  8. Run test scripts on RC
Tested bySuccess?
RC-1
Success?
RC-2
Success?
RC-3
Notes
Danny Bernstein

(tick)





Resources

[1] Testing scripts

[2] Fedora 4 Release Test Suite

  • No labels