Versions Compared

Old Version 3

changes.mady.by.user Yinlin Chen

Saved on

compared with

New Version Current

changes.mady.by.user Ben Pennell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Testing

...

 

Blocker Tickets

  • ...

External Projects

Samvera

Project

Tested by

Success? RC-1

Notes

ActiveFedora




CurationConcerns




Hyrax


Plum




Islandora

 Project

Tested

 Test steps Platform Tested

by

Success?

 

 RC-1

Notes

Islandora 8




Testing Plan

Code Block
git clone https://github.com/fcrepo/fcrepo
cd fcrepo
git checkout <version>-RC

Sanity Builds

Scripts

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

ProjectCommandPlatformTested bySuccess?Notes
fcrepomvn clean install

linux




fcrepomvn clean install mac 


fcrepomvn clean installwindows


One-Click Run

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


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


java -jar

Fedora <version> Web Application  Linux   Fedora <version> Web Application Windows   Fedora <version> One-click-run Application
  • mvn clean install
    • java -jar ./fcrepo-webapp/target/

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

    Linux   Fedora <version> One-click-run Application Windows   Fedora<version> Vagrant

    		Windows


    Manual Tests

    Info

    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)

    DatabasePlatform
    Test steps
    Tested 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 - Outdated, needs docker replacement.

    Code Block
    vagrant destroy
vagrant up


    Test stepsTested bySuccess?Notes

    FEDORA_AUTH=true




    FEDORA_AUTH=false




    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.0 one-click
    2. Load sample datasets via /fcr:restore
    3. Run test scripts on 4.7.0
    4. Stop 4.7.0
    5. Start RC one-click
    6. Run test scripts on RC
    7. ReStart RC
    8. Run test scripts on RC
    Tested bySuccess RC2Notes






    Resources

    [1] Testing scripts

    [2] Fedora 4 Release Test Suite

     

    Verify scripts: