Release Test Iteration 5 succestest

Purpose

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.

Release Test Iteration 5 failure (broken objects) test

Purpose

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.

Release Test Iteration 5 (Broken folder structure) test

Purpose

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.

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

Purpose

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.

Release Test Iteration 5 (Connection dies while ingesting) test

Purpose

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.