• Iteration7ReleaseTest

Release Test Iteration 7

Release Test Iteration 7 - Successful harvest of DOMS data

ABR: 5 md spent writing and updating this text throughout the iteration. 4 md spent bugfixing in relation to this, mainly in modules from last iteration.

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.

Release Test Iteration 7 - Check preingest - failed

Purpose

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.

Release Test Iteration 7 - Check direct disseminator call - failed

Purpose

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.

Release Test Iteration 7 - Perform OAI harvest - failed

Purpose

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.