## Action
= Action Releasetest 5 =

## Detailed description of wanted output from the work to be carried out.
## E.g. Implement a utility class for writing data to a disk. The data must be base64 encoded before being written.

'''Success test''':

The releasetest for iteration 5 should encompass running the migrated ingest code on a number of test objects, and see that these are ingested in Fedora.

The ingested test objects should be Gentofte examples including raw data (files). The action "[[ActionGentofte|Identify "Gentofte" objects, design datamode]]" is responsible for creating these objects.

We will need to communicate closely with the [[ActionDesignAndSalvageIngestModule|action defining ingest]] before we can define the releasetest.

'''Test of correct behaviour on failures''':

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

 * Invalid XML files
 * Invalid package folder structure
 * No contact to Fedora.
 * Lost contact while ingesting

'''Estimate required time for running release test''':

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

<<BR>>

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

We should create some Wikipage templates for creating releastest descriptions.


=== Estimated time ===

 * Writing and estimating this specific release test: 1 md.
  * Success test
  * Failure tests
 * Writing release test guidelines and templates: 2 md.



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