Testing Tickets

RC-1 Testing

• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Defer to 5.1

• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.

RC-2 Testing

• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.

External Projects

Samvera (instructions)

Project	Tested by	Success? RC-1	Success? RC-2	Notes
valkyrie	Esmé Cowles			Using branch: fedora_5_escowles

Islandora (testing ticket)

API-X

Testing Plan

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


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

Sanity Builds

Scripts

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

Project	Command	Platform	Tested By	RC 1	RC 2	Notes
fcrepo4	mvn clean install	linux	Yinlin Chen Andrew Woods Randall Floyd			Build successfully in Ubuntu Server 16.04 LTS (HVM) Build successful on Fedora Linux 27; openjdk version "1.8.0_191"; Maven 3.5.0 (Red Hat 3.5.0-6)
fcrepo4	mvn clean install	mac	Yinlin Chen			Build successfully
fcrepo4	mvn clean install	windows				Does not compile on Windows 10 https://gist.github.com/robyj/ac6de53305cf8e903cf63268ad736a9b

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

API-Test Suite

1. Start Fedora with the following command

   mvn jetty:run -Dfcrepo.external.content.allowed=fcrepo-http-api/src/test/resources/allowed_external_paths.txt -Dfcrepo.auth.webac.userAgent.baseUri=http://example.com/ -pl fcrepo-webapp/

2. Run the API-Test suite with the following command

   java -jar target/testsuite-1.0-SNAPSHOT-shaded.jar -c config-local.yml

   1. Where "config-local.yml" is something like the following

      default:
        rooturl: http://localhost:8080/rest/
        root-controller-user-webid: http://example.com/fedoraAdmin
        root-controller-user-name: fedoraAdmin
        root-controller-user-password: fedoraAdmin
        permissionless-user-webid: http://example.com/testuser
        permissionless-user-name: testuser
        permissionless-user-password: testpass
        broker-url: tcp://127.0.0.1:61616
        topic-name: fedora
        queue-name: 
        testngxml: testng-local.xml
        implementation-name: Fedora
        implementation-version: 5.0.0-RC
      tomcat:
        rooturl: http://localhost:8080/fcrepo/rest/
        root-controller-user-webid: http://example.com/fedoraAdmin
        root-controller-user-name: fedoraAdmin
        root-controller-user-password: secret3
        permissionless-user-webid: http://example.com/testuser
        permissionless-user-name: testuser
        permissionless-user-password: password1
        broker-url: tcp://127.0.0.1:61616
        topic-name: fedora
        queue-name: 
        testngxml: testng-local.xml
        implementation-name: Fedora
        implementation-version: 5.0.0-RC

One-Click Run

cd fcrepo-webapp; mvn clean install -Pone-click

Command	Platform	Tested By	RC-1	RC-2	Notes
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar	Linux	Andrew Woods			Ran one-click and successfully performed manual tests
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar	Mac	Yinlin Chen			Build and start One-Click run successfully
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar	Windows

Manual Tests

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

WebAC Tests

Use the following recipes to create WebAC-protected resources

Default ACL

1. Create resource
2. Verify expected access privileges based on default (root) ACL

Simple read-only

1. Create resource to protect
2. Create ACL on protected resource (read-only)
3. Create child of protected resource
4. Verify expected access privileges on target and child

Simple read-write

1. Create resource to protect
2. Create ACL on protected resource (read/write)
3. Create child of protected resource
4. Verify expected access privileges on target and child

External Content

Create and verify all three modes of external content handling: proxy, redirect, copy

Database Tests

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

Database	Platform	Tested by	Success RC1?	Success RC2	Notes
MySQL	macOS	James Silas Creel			High Sierra 10.13.6, MySQL 8.0.13
PostgreSQL	macOS	James Silas Creel			High Sierra 10.13.6, PostgreSQL 9.6.2
PostgreSQL	linux	Yinlin Chen			Ubuntu 16.04, PostgreSQL 9.4.20
MySQL5.6	linux	Yinlin Chen			Ubuntu 16.04, Mysql 5.7.24
PostgreSQL	windows	Jon Roby			version 11.0-2
MySQL5.6	windows	Jon 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.

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

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

Resources

[1] Testing scripts

[2] Fedora 4 Release Test Suite