## Action
= Action Release Test for Iteration 6 =

== Success test ==

The releasetest for iteration 6 should encompass running the preingest code on a number of Gentofte objects, and compare the FoxML output to guaranteed valid objects. If they are valid, we should ingest the objects via the ingest module, to see if Fedora understands them correctly.

For that reason, we need to craft guaranteed valid objects by some other means than the preingest module. 


## == Test of correct behaviour on failures ==

## We must assert that we fail gracefully in the following cases:

## * Invalid/missing metadata files
## * Invalid metadata folder structure
## * Errors in the FoxML templates

== Estimate required time for running release test ==

Once we have written the tests, we should estimate the time required to run them.

It will also be part of this action to define the framework for running releasetests on the preingester, since it doesn't exist yet. We should have some wikipages and some rules for how to "run" the releasetest.

Bugfixing will be considered an integral part of running the release test, and the time estimation should reflect this. 


=== Estimated time ===

 * (0.5md) Writing and estimating this specific release test
  * Success test
 * (3md worstcase) Creating the nessesary install scripts and guaranteed valid objects
 * (3md) Running the release tests and doing bug-fixes


=== Review comments from KFC ===

DONE: Is the 'Test of correct behaviour on failures' simply legacy? It does not seem to be updated from releasetest 5.

DONE: Shouldn't we run the ingest code on the generated objects, to ensure they are suitable for our designed purpose?

## Targeted WBS Tasks and Assigned Developers can be found on the iteration page for this action.