Release test
The release test consists of the following (TODO: Still needs to be fleshed out some more)
The objects chosen for the first step of the release test are:
- Volume Vol. 1
- Region København (Contains Town 1)
- Region Holstein (Contains Town 200 - 275)
- Town 1 (København)
- Town 207 (Segeberg)
- Town 200 (Kiel)
- Paper 1-18
- Paper 1-19
- Paper 200-1
- Paper 200(1771)
- Paper 207-1
- Page 1_86
- Page 1_293
- Page 1_300
- PNG dda1_86
- PNG dda1_293
- PNG dda1_300
The steps of the test itself are:
- Success test
- Human inspection of preingest FoxML output by comparing the output objects with objects prepared beforehand (available "here").
- Ingest into Fedora (seeing if Fedora accepts the FoxML objects).
- Inspection of the objects in Fedora (by use of admin application)
- Failure tests
- Test of correct behaviour on failures, ensuring that they are "failing gracefully".
Purpose
Test the Simple Preingest, in particular with the following problems:
- missing pages in sequence
- invalid png-files
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 |
Purpose
Testing the Full Preingest
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 |
Purpose
Check the direct disseminator call
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 |
Purpose
Test whether harvester generates the expected output.
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 |