Versions Compared

Key

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

...

Project

Tested by

Success? RC-1

Notes

ActiveFedora

(tick)


CurationConcerns

(tick)


Hyrax

(tick)

(tick)

(tick)


Plum (tick)
 
Sufia (tick)
 

Islandora

 Project

Tested by

Success? RC-1

Notes

CLAW(tick)#IslandoraCon demo works fine with 4.7.3-RC1

...

DatabasePlatformTested bySuccess?Notes
MySQL MacOSX 10.11.6
MySQL 5.7.17
 (tick)

 

PostgreSQL   MacOSX 10.12.5
PostgreSQL 9.4.5
Esmé Cowles(tick) 

fcr:backup/fcr:restore Functionality

...

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                  

LinuxJettyfile-simple4.7.24.7.310010032-M(tick)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 stepsTested bySuccess?Notes

FEDORA_AUTH=true
FEDORA_AUDIT=true

  

(tick)

(tick)

 

FEDORA_AUTH=false
FEDORA_AUDIT=true

 

(tick)

(tick)

 

FEDORA_AUTH=true
FEDORA_AUDIT=false

 

(tick)

(tick)

 

FEDORA_AUTH=false
FEDORA_AUDIT=false

 

(tick)

(tick)

 

Manual Tests

Same as above, plus:

  1. Verify audit events are in triplestore (tick)
  2. Verify resources are in triplestore (tick) (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)
  3. Verify resources are in Solr (tick)
  4. Verify authorization works for the two auth-enabled configurations (tick)
  5. Verify reindexing to triplestore works (tick) (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

...

  1. 4.7.2
    1. Start 4.7.0 with a new data directory
    2. Create a resource with SKOS namespace
      1. 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/

    3. Stop 4.7.0 and start
    4. Start 4.7.2 with the same data directory should start successfully
    5. 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
  2. 4.7.3
    1. 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 bySuccess?Notes
(tick)




[1] Testing scripts

[2] Fedora 4 Release Test Suite