Issues found during testing
- RC-1
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2370 |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2371 |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2374 |
---|
|
- not merged into master Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2375 |
---|
|
- not merged into master Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-2376 |
---|
|
- will not resolve in 4.7.1
- RC-2
External Projects
Hydra
Project | Tested by | Success? RC-1 | Success? RC-2 | Notes |
---|
ActiveFedora | | ![(error)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/error.svg) | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | I see two test failures when running the ActiveFedora tests with 4.7.1-RC-1 ( error log ). The root cause seems to be that a HEAD request with an invalid namespace returns 400 Bad Request with 4.7.1-RC-1, instead of 404 Not Found (as it does in 4.7.0). |
CurationConcerns | | | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
Plum | | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
Sufia | | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
Islandora
Project | Tested by | Success? RC-1 | Success? RC-2 | Notes |
---|
CLAW | | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
Testing Blocker Tickets
External Projects
Testing Plan
Code Block |
---|
git clone https://github.com/fcrepo4/fcrepo4
cd fcrepo4
git checkout <version>4.7.1-RC |
Sanity Builds
Filesystem Federation
Test simple federation
![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | Windows 10 |
One-Click Run
cd fcrepo-webapp; mvn clean install -Pone-click
Manual Tests
Info |
---|
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? RC-1 | Success? RC-2 | Notes |
---|
MySQL | 5.6.34 MySQL Community Server (GPL) (rh-mysql56) on RHEL 7.3 | Jim Coble | | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | Performed Manual Tests listed above. Also ran script that created 200,000 objects and then versioned them. |
PostgreSQL | Postgres9.4 on Docker | | | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
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
No Format |
---|
|
# 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 | Tomcat (7.0.72) | Postgres (9.4) | 4.6.1 | 4.7.1-RC1 | 461,568 | 1,671 | 48G | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
| Mac | Jetty (Standalone) | | 4.7.1-RC1 | 4.7.1-RC1 | 25,600 | 0 | | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
| Mac | Jetty (Standalone) | | 4.7.1-RC1 | 4.7.1-RC1 | 12,800 | 12,800 | 13GB | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
| Mac | Jetty (Standalone) | | 4.7.1-RC1 | 4.7.1-RC2 | 12,800 | 12,800 | 13GB | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
| Docker | Tomcat7 | Postgres 9.4 | 4.7.1-RC2 | 4.7.1-RC2 | 25,600 | 0 | 3.8M | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
| Docker | Tomcat7 | Postgres 9.4 | 4.7.1-RC2 | 4.7.1-RC2 | 2560 | 2560 | 2.7G | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
| Linux | Tomcat (7.0.72) | Postgres 9.4 | 4.6.1 | 4.7.1-RC2 | 461,568 | 1,671 | 48G | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
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.
Multi-thread Tests
These tests are designed to ensure the integrity of the repository when loading content in a multi-threaded fashion. Testing for repository corruption should entail confirming the successful load of resources, the successful fetching of resources, and the successful deletion of resources. Prior to 4.6.1, these tests would result in repository corruption.
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. See the README for more info.
Tested by | Platform | Container (Tomcat/Jetty) | Database Backend | Number of Threads | Number of RDF Resources | Number of Binaries | Success? RC-1 | Success? RC-2 | Notes |
---|
| Mac | Jetty (Standalone) | | 2 | 12,800 | 12,799 | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | | Tried to load 12,800 binary resources, but 1 binary resource resulted in a 4xx error during load. This was a failed ingest so in the end the successful 201s matched the 200s during verification. |
| Mac | Jetty (Standalone) | | 8 | 12,800 | 12,706 | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | | Tried to load 12,800 binary resources, but 94 binary resources resulted in 500 errors during load. These were failed ingests so in the end the successful 201s matched the 200s during verification. |
| Mac |
| PostgreSQL | | | | Jetty (Standalone) | | 8 | 25,600 | 0 | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | | |
| Mac | Jetty (Standalone) | | 8 | 25,600 | 0 | | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
| Docker | Tomcat7 | Postgres9.4 | 8 | 25,600 | 0 | | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
| Docker | Tomcat7 | Postgres9.4 | 4 | 2560 | 2560 | | ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
NB: "Success" is measured by receiving all 200s when performing a GET on each loaded resource, and all 204s when finally deleting the content.
Vagrant Tests
Code Block |
---|
vagrant destroy
vagrant up |
Test steps | Tested by | Success? RC-1 | Success? RC-2 | Notes |
---|
FEDORA_AUTH=true FEDORA_AUDIT=true |
| | | -
| - ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
FEDORA_AUTH=false FEDORA_AUDIT=true |
| | -
| - ![(tick)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/check.svg) | |
FEDORA_AUTH=true FEDORA_AUDIT=false |
| Manual Tests
Same as above, plus:
...