|
Size: 3949
Comment:
|
Size: 2406
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 42: | Line 42: |
| The steps of the test itself are: | [[BR]] The release test consists of |
| Line 45: | Line 48: |
| Test that the system responds as expected when presented with valid data. 2. Failure tests Test of correct behaviour on failures, ensuring that they are "failing gracefully". Each table below describes the steps needed to complete the release test. 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. The notes fields can be used for comments about the test. == Success test == ||'''Test step'''||'''Status'''||'''Notes'''|| || || || || |
|
| Line 49: | Line 71: |
| 2. Failure tests Test of correct behaviour on failures, ensuring that they are "failing gracefully". |
== Failure test - Simple preingester fails == |
| Line 57: | Line 79: |
| Line 59: | Line 80: |
| 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. |
|
| Line 68: | Line 82: |
| || || || || == Failure test - Full preingester fails == |
|
| Line 72: | Line 90: |
| Line 74: | Line 91: |
| 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. |
|
| Line 83: | Line 93: |
| || || || || == Failure test - Direct disseminator call fails == |
|
| Line 87: | Line 101: |
| Line 89: | Line 102: |
| 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. |
|
| Line 98: | Line 104: |
| || || || || == Failure test - Performing OAI harvest fails == |
|
| Line 102: | Line 112: |
| Line 104: | Line 113: |
| 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. |
|
| Line 113: | Line 115: |
| || || || || |
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 release test consists of
- Success test
- Test that the system responds as expected when presented with valid data.
- Failure tests
- Test of correct behaviour on failures, ensuring that they are "failing gracefully".
Each table below describes the steps needed to complete the release test. 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.
The notes fields can be used for comments about the test.
Success test
Test step |
Status |
Notes |
|
|
|
- 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 test - Simple preingester fails
Purpose
Test the Simple Preingest, in particular with the following problems:
- missing pages in sequence
- invalid png-files
Steps
Test step |
Status |
Notes |
|
|
|
Failure test - Full preingester fails
Purpose
Testing the Full Preingest
Steps
Test step |
Status |
Notes |
|
|
|
Failure test - Direct disseminator call fails
Purpose
Check the direct disseminator call
Steps
Test step |
Status |
Notes |
|
|
|
Failure test - Performing OAI harvest fails
Purpose
Test whether harvester generates the expected output.
Steps
Test step |
Status |
Notes |
|
|
|