Project | Tested by | Success? RC-1 | Notes |
---|---|---|---|
Project | Tested by | Success? RC-1 | Notes |
---|---|---|---|
CLAW? |
Project | Tested by | Success? RC-1 | Notes |
---|---|---|---|
fcrepo-api-x-integration | |||
fcrepo-api-x-demo (Docker) |
git clone https://github.com/fcrepo4/fcrepo4 cd fcrepo4 git checkout 5.0.0-RC |
https://github.com/awoods/fcrepo-build-scripts
Project | Command | Platform | Tested By | RC 1 | Notes |
---|---|---|---|---|---|
fcrepo4 | mvn clean install | linux | |||
fcrepo4 | mvn clean install | mac | |||
fcrepo4 | mvn clean install | windows |
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
cd fcrepo-webapp; mvn clean install -Pone-click
Command | Platform | Tested By | RC-1 | Notes |
---|---|---|---|---|
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar | Linux | |||
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar | Mac | |||
java -jar fcrepo-webapp-<version>-SNAPSHOT-jetty-console.jar | Windows |
All of the below should take place in the HTML UI and non-vagrant tests should run against fcrepo-webapp-plus. |
With Tomcat7 deployment, run above manual tests with alternate backend databases (Configuring JDBC Object Store)
Database | Platform | Tested by | Success RC1? | Notes |
---|---|---|---|---|
MySQL | osx | |||
PostgreSQL | osx | |||
PostgreSQL | linux | |||
MySQL5.6 | linux | |||
PostgreSQL | linux | |||
MySQL5.6 | linux |
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
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 RC1? | Success RC2? | Notes |
---|---|---|---|---|---|---|---|---|---|---|---|
Linux | Jetty | File-simple | |||||||||
Linux | Tomcat | Postgres | |||||||||
Linux | Tomcat | Postgres | |||||||||
Linux | Tomcat | Postgres | |||||||||
Linux | Tomcat | Mysql | |||||||||
Linux | Tomcat | Mysql 5.6 | |||||||||
Linux | Tomcat | Postgres |
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 destroy vagrant up |
Test steps | Tested By | Success RC2? | Notes |
---|---|---|---|
FEDORA_AUTH=true | |||
FEDORA_AUTH=false | |||
FEDORA_AUTH=true | |||
FEDORA_AUTH=false |
Same as above, plus:
(for reference: https://docs.google.com/presentation/d/1aU-qRVmU0lB18ywepk2AGYEmRe-HfIwhUaofHgathGQ/edit#slide=id.g11caa1fd99_0_0)
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"]' |
Tested by | Success RC1 | Notes |
---|---|---|
[1] Testing scripts
[2] Fedora 4 Release Test Suite