= Release Test Iteration 5 succestest =
## Replace TITLE above with a name for this test

== Purpose ==
## Describe the overall purpose of this test

Tests successful scenario of ingest

== Steps ==
This table describes the steps needed to complete the releasetest. Subpages describe the details of what you should do in the step.

On each step, do what the subpage describes. Then mark the status column with "OK" or "Fail" depending on whether the step was succesful or not.

If the step is unsuccesful, you report the problem to bugzilla, and the QA master must decide whether the bug is important enough that it needs to be fixed before release. In that case the releasetest needs to restart after the bug is fixed.

The notes field can be used for comments about the test.

||'''Test step'''||'''Status'''||'''Notes'''||
## ||[:UnpackTestStep:Unpack the code]||OK|| ||
## ||[:StartTestStep:Start program X]||OK|| ||
## ||[:ClickFooTestStep:Click the foo button]||OK|| ||
## ||[:CheckFooResultTestStep:Check that foo happened]||Fail||Bug 42 reported||
## ||[:ShutDownTestStep:Shut the system down]|| || ||
||[[RunTestSetupTestStep|Run the test setup with blank install]]|| OK || ||
||[[InstallIngestPackageTestStep|Install the ingest package]]|| OK || ||
||[[CheckoutDOMSObjectsTestStep|Checkout the DOMS objects]]|| OK || ||
||[[CheckoutGentofteObjectsTestStep|Checkout the Gentofte objects]]|| OK || ||
||[[IngestObjectsTestStep|Ingest the objects]]|| OK || ||
||[[CheckResultsTestStep|Check the results]]|| OK || Bug 234 was ignored in this test ||

= Release Test Iteration 5 failure (broken objects) test =
## Replace TITLE above with a name for this test

== Purpose ==
## Describe the overall purpose of this test

Tests graceful handling of a realistic error

== Steps ==
This table describes the steps needed to complete the releasetest. Subpages describe the details of what you should do in the step.

On each step, do what the subpage describes. Then mark the status column with "OK" or "Fail" depending on whether the step was succesful or not.

If the step is unsuccesful, you report the problem to bugzilla, and the QA master must decide whether the bug is important enough that it needs to be fixed before release. In that case the releasetest needs to restart after the bug is fixed.

The notes field can be used for comments about the test.

||'''Test step'''||'''Status'''||'''Notes'''||
## ||[:UnpackTestStep:Unpack the code]||OK|| ||
## ||[:StartTestStep:Start program X]||OK|| ||
## ||[:ClickFooTestStep:Click the foo button]||OK|| ||
## ||[:CheckFooResultTestStep:Check that foo happened]||Fail||Bug 42 reported||
## ||[:ShutDownTestStep:Shut the system down]|| || ||
||[[RunTestSetupTestStep|Run the test setup with blank install]]|| OK || ||
||[[InstallIngestPackageTestStep|Install the ingest package]]|| OK || ||
||[[CheckoutDOMSObjectsTestStep|Checkout the DOMS objects]]|| OK || ||
||[[CheckoutGentofteObjectsTestStep|Checkout the Gentofte objects]]|| OK || ||
||[[SabotageObjectsTestStep|Sabotage objects]]|| OK || ||
||[[IngestObjectsWithFailureTestStep|Ingest the objects]]|| OK || ||
||[[CheckIngestFailureTestStep|Check the failure output]]|| OK || Bug 246 ignored in this test ||

= Release Test Iteration 5 (Broken folder structure) test =
## Replace TITLE above with a name for this test

== Purpose ==
## Describe the overall purpose of this test

Tests graceful handling of a realistic error

== Steps ==
This table describes the steps needed to complete the releasetest. Subpages describe the details of what you should do in the step.

On each step, do what the subpage describes. Then mark the status column with "OK" or "Fail" depending on whether the step was succesful or not.

If the step is unsuccesful, you report the problem to bugzilla, and the QA master must decide whether the bug is important enough that it needs to be fixed before release. In that case the releasetest needs to restart after the bug is fixed.

The notes field can be used for comments about the test.

||'''Test step'''||'''Status'''||'''Notes'''||
## ||[:UnpackTestStep:Unpack the code]||OK|| ||
## ||[:StartTestStep:Start program X]||OK|| ||
## ||[:ClickFooTestStep:Click the foo button]||OK|| ||
## ||[:CheckFooResultTestStep:Check that foo happened]||Fail||Bug 42 reported||
## ||[:ShutDownTestStep:Shut the system down]|| || ||
||[[RunTestSetupTestStep|Run the test setup with blank install]]|| OK || ||
||[[InstallIngestPackageTestStep|Install the ingest package]]|| OK || ||
||[[CheckoutDOMSObjectsTestStep|Checkout the DOMS objects]]|| OK || ||
||[[CheckoutGentofteObjectsTestStep|Checkout the Gentofte objects]]|| OK || ||
||[[SabotageFileStructureTestStep|Sabotage folder structure]]|| OK || ||
||[[IngestObjectsWithFailureTestStep|Ingest the objects]]|| OK || ||
||[[CheckDirectoryFailureTestStep|Check the failure output]]|| OK || ||



= Release Test Iteration 5 (no Fedora to connect to) test =


== Purpose ==
## Describe the overall purpose of this test

Tests graceful handling of a realistic error


== Steps ==
This table describes the steps needed to complete the releasetest. Subpages describe the details of what you should do in the step.

On each step, do what the subpage describes. Then mark the status column with "OK" or "Fail" depending on whether the step was succesful or not.

If the step is unsuccesful, you report the problem to bugzilla, and the QA master must decide whether the bug is important enough that it needs to be fixed before release. In that case the releasetest needs to restart after the bug is fixed.

The notes field can be used for comments about the test.

||'''Test step'''||'''Status'''||'''Notes'''||
## ||[:UnpackTestStep:Unpack the code]||OK|| ||
## ||[:StartTestStep:Start program X]||OK|| ||
## ||[:ClickFooTestStep:Click the foo button]||OK|| ||
## ||[:CheckFooResultTestStep:Check that foo happened]||Fail||Bug 42 reported||
## ||[:ShutDownTestStep:Shut the system down]|| || ||
||[[RunTestSetupTestStep|Run the test setup with blank install]]|| OK || ||
||[[StopFedoraIfItExists|Stop Fedora]]|| OK || ||
||[[InstallIngestPackageTestStep|Install the ingest package]]|| OK || ||
||[[CheckoutDOMSObjectsTestStep|Checkout the DOMS objects]]|| OK || ||
||[[CheckoutGentofteObjectsTestStep|Checkout the Gentofte objects]]|| OK || ||
||[[IngestObjectsWithFailureTestStep|Ingest the objects]]|| OK || ||
||[[CheckConnectionFailureResultsTestStep|Check the connection failure output]]|| OK || ||


= Release Test Iteration 5 (Connection dies while ingesting) test =

== Purpose ==
## Describe the overall purpose of this test

Tests graceful handling of a realistic error

== Steps ==
This table describes the steps needed to complete the releasetest. Subpages describe the details of what you should do in the step.

On each step, do what the subpage describes. Then mark the status column with "OK" or "Fail" depending on whether the step was succesful or not.

If the step is unsuccesful, you report the problem to bugzilla, and the QA master must decide whether the bug is important enough that it needs to be fixed before release. In that case the releasetest needs to restart after the bug is fixed.

The notes field can be used for comments about the test.

||'''Test step'''||'''Status'''||'''Notes'''||
## ||[:UnpackTestStep:Unpack the code]||OK|| ||
## ||[:StartTestStep:Start program X]||OK|| ||
## ||[:ClickFooTestStep:Click the foo button]||OK|| ||
## ||[:CheckFooResultTestStep:Check that foo happened]||Fail||Bug 42 reported||
## ||[:ShutDownTestStep:Shut the system down]|| || ||
||[[RunTestSetupTestStep|Run the test setup with blank install]]|| OK || ||
||[[InstallIngestPackageTestStep|Install the ingest package]]|| OK || ||
||[[CheckoutDOMSObjectsTestStep|Checkout the DOMS objects]]|| OK || ||
||[[CheckoutGentofteObjectsTestStep|Checkout the Gentofte objects]]|| OK || ||
||[[IngestObjectsButKillFedoraWhileIngestingTestStep|Ingest the objects, but kill fedora while ingesting]]|| OK || ||
||[[CheckConnectionF0ailureTestStep|Check the connection failure output]]|| OK || Test description changed to reflect the fact that all files are placed in failure/base at failure, no success directory is generated ||