Page tree
Skip to end of metadata
Go to start of metadata

Testing Tickets

RC-1 Testing


External Projects

Samvera (instructions)

Project

Tested by

Success? RC-1

Notes






Islandora (testing ticket)

 Project

Tested by

Success? RC-1

Notes

CLAW





API-X

 Project

Tested by

Success? RC-1

Notes

fcrepo-api-x-integration




fcrepo-api-x-demo (Docker)


Testing Plan

git clone https://github.com/fcrepo4/fcrepo4
cd fcrepo4
git checkout fcrepo-5.0.0-RC-1


# or pull pre-built resources from https://github.com/fcrepo4/fcrepo4/releases/tag/fcrepo-5.0.0-RC-1

Sanity Builds

Scripts

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

ProjectCommandPlatformTested ByRC 1Notes
fcrepo4mvn clean install

linux

(tick) Build successfully in Ubuntu Server 16.04 LTS (HVM)
fcrepo4mvn clean install mac (tick)Build successfully
fcrepo4mvn clean installwindows


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
CommandPlatformTested ByRC-1Notes
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jarLinux(error)

BUILD FAILURE: [WARNING] The POM for org.fcrepo:fcrepo-kernel-modeshape:jar:5.0.0-SNAPSHOT is missing.

But, build from current master branch run successfully

java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jarMac(tick) Build and start One-Click run successfully

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

Database Tests

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

DatabasePlatformTested bySuccess RC1?Notes
MySQLmacOS(tick)High Sierra 10.13.6, MySQL 8.0.13
PostgreSQLmacOS(tick)High Sierra 10.13.6, PostgreSQL 9.6.2
PostgreSQLlinux(tick)Ubuntu 16.04, PostgreSQL 9.4.20
MySQL5.6linuxYinlin Chen(tick)Ubuntu 16.04, Mysql 5.7.24
PostgreSQLwindowsJon Roby
version 11.0-2
MySQL5.6windowsJon Roby

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

Success RC2?

Notes                  

LinuxJettyFile-simple








LinuxTomcatPostgres








LinuxTomcatPostgres








LinuxTomcatPostgres








LinuxTomcatMysql








LinuxTomcatMysql 5.6








LinuxTomcatPostgres







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

FEDORA_AUTH=true
FEDORA_AUDIT=false




FEDORA_AUTH=false
FEDORA_AUDIT=false




FEDORA_AUTH=true
FEDORA_AUDIT=true




FEDORA_AUTH=false
FEDORA_AUDIT=true




Manual Tests

Same as above, plus:

(for reference: https://docs.google.com/presentation/d/1aU-qRVmU0lB18ywepk2AGYEmRe-HfIwhUaofHgathGQ/edit#slide=id.g11caa1fd99_0_0)

  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

    vagrant ssh
    sudo service tomcat7 stop
    sudo rm -rf /etc/fuseki/databases/test_data/*
    sudo service tomcat7 start
    curl -XPOST localhost:9080/reindexing/ -H"Content-Type: application/json" -d '["activemq:queue:triplestore.reindex"]'

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 RC1Notes







Resources

[1] Testing scripts

[2] Fedora 4 Release Test Suite

  • No labels