Fedora relies on and appreciates members of the Fedora community participating in testing release candidates during a Fedora release to ensure new releases are ready for their use.
This page is to give some basic information on
Participation
To participate, there will be a new page created as a child of this page with a title of "Release Testing - <version number>".
Each section normally has a table similar to (but not necessarily containing all columns)
| Test | Platform | Tested By | Success? RC-N | Notes |
|---|---|---|---|---|
| The test being run | The platform being tested (Linux, Windows, Mac) | Your name |  or  ( / ) or ( x ) but with no spaces inside the brackets | Any additional information you want to record |
| Example: sanity build | OSX | |
Perform any tests you can, and record the results. Also if there are specific use cases for your use of Fedora, feel free to test those cases as well and let us know.
Testing failures
If there is a failed test or you discover a problem, that will result in a fix being required and new release candidate to be pushed out. Please ensure to document any issues you encounter.
Test Sections
Below are the "tests" on past and current release testing documents with some information.
External Projects
Projects that have a historical relationship with Fedora. We ask a member of that community to try using the new version within their setup to ensure they will experience no issues.
Sanity Builds
Simply Git clone the repository and attempt to build the code
mvn clean install
One-Click Run - Deprecated
In past a clickable jar file was created to allow easy use of Fedora, this has been removed in new versions as Java version changes made it hard to make workable.
Manual Tests
The HTML UI needs to be replaced ( FCREPO-3900 - Getting issue details... STATUS ) but to ensure current functionality remains. We ask that you run Fedora and perform the listed tests using the HTML UI.
This normally done just using
cd fcrepo mvn clean install cd fcrepo-webapp mvn jetty:run
Database Tests
This is actually just running the above manual tests but setting Fedora up to use a database instead of the internal H2 database.
fcr:backup/fcr:restore Functionality
These tests and the associated endpoints were deprecated in Fedora 4.7.1 and removed in Fedora 6.0.0. They no longer need to be run. In past these tested the ability to roundtrip data out of and back in to a Fedora repository.
Vagrant Tests - Outdated, needs docker replacement.
As noted in the title, these tests need work. Ideally these tests could be run with the docker-compose container available in the fcrepo-camel-toolbox with some work done to add instructions to using a release candidate Fedora as a container.
Backwards Compatibility Tests
This again uses the backup and restore functionality. It is no longer tested as now Fedora sits on an OCFL layer which allows a more consistent storage format.
