...
Project | Tested by | Success? RC-1 | Notes |
---|---|---|---|
ActiveFedora | |||
CurationConcerns | |||
Hyrax | |||
Plum | |||
Sufia |
...
Database | Platform | Tested by | Success? | Notes | |||
---|---|---|---|---|---|---|---|
MySQL | MacOSX 10.11.6 MySQL 5.7.17 | |
| ||||
PostgreSQL | MacOSX 10.12.5 PostgreSQL 9.4.5 | Esmé Cowles |
fcr:backup/fcr:restore Functionality
...
Tested by | Platform | Container (Tomcat/Jetty) | Database Backend | From Fedora | To Fedora | Number of RDF Resources | Number of Binaries | Size of Backup (du -h .) | Success? | Notes |
---|---|---|---|---|---|---|---|---|---|---|
Linux | Jetty | file-simple | 4.7.2 | 4.7.3 | 100 | 100 | 32-M | plantpatents dataset |
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.
...
Test steps | Tested by | Success? | Notes |
---|---|---|---|
FEDORA_AUTH=true | |||
FEDORA_AUTH=false |
| ||
FEDORA_AUTH=true | |||
FEDORA_AUTH=false |
Manual Tests
Same as above, plus:
- Verify audit events are in triplestore
- Verify resources are in triplestore (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)
- Verify resources are in Solr
- Verify authorization works for the two auth-enabled configurations
- Verify reindexing to triplestore works (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
...
- 4.7.2
- Start 4.7.0 with a new data directory
- Create a resource with SKOS namespace
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/
- Stop 4.7.0 and start
- Start 4.7.2 with the same data directory – should start successfully
- Stop and start 4.7.2 with the same data directory – should display error on startupView the record from 1.b. ??Note: this did not reproduce the error for me
- 4.7.3
- Repeat 1. with a clean data directory, but deploying 4.7.3 instead of 4.7.2 and verifying that the error does not occur
Tested by | Success? | Notes |
---|---|---|
[1] Testing scripts