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

1. Success test
   • 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

Purpose

Test that the system responds as expected when presented with valid data.

Steps

Failure test - Simple preingester fails on missing pages

Purpose

Test that teh system fails gracefully (with meaningful error message) when receiving a sequence of pages that has missing pages in the sequence.

Steps

Note: It might (not) be relevant to test what happens when pre-ingester receives invalid png-files.

Failure test - Simple preingester fails on filename anomalies

Purpose

Test that teh system fails gracefully (with meaningful error message) when receiving a sequence of pages that includes pages with filename anomalies.

Steps

Failure test - Simple preingester fails on last page missing

Purpose

Test that teh system fails gracefully (with meaningful error message) when receiving a sequence of pages where the last page is missing.

Steps

Failure test - Simple preingester fails on too many pages

Purpose

Test that teh system fails gracefully (with meaningful error message) when receiving a sequence of pages with too many pages compared to the number in BIND_x.xml.

Steps

Failure test - Full preingester fails on empty xml file

Purpose

Test that teh system fails gracefully (with meaningful error message) when one of the xml files is empty

Steps

Failure test - Full preingester fails on mismatching pagenumbers

Purpose

Test that teh system fails gracefully (with meaningful error message) when the two occurrences of the pagenumber at imagefile and pagenumber are not matching.

Steps

Failure test - Full preingester fails on nonexistent imagefile

Purpose

Test that teh system fails gracefully (with meaningful error message) when the imagefile referred to in the xml is non-existent.

Steps

Failure test - Direct disseminator call fails

Purpose

Ingest an object and its (faulty) disseminator, so that the webservice will crash. Check that in the end, the result in Summa is acceptable.

Steps

Failure test - Performing OAI harvest fails

Purpose

Test whether harvester generates the expected output.

Steps