|
⇤ ← Revision 1 as of 2008-06-26 12:26:08
Size: 8333
Comment: Created by the PackagePages action.
|
← Revision 2 as of 2010-03-17 13:09:09 ⇥
Size: 8366
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 24: | Line 24: |
| ||[:RunTestSetupTestStep:Run the test setup with blank install]|| OK || || ||[:InstallIngestPackageTestStep:Install the ingest package]|| OK || || ||[:CheckoutDOMSObjectsTestStep:Checkout the DOMS objects]|| OK || || ||[:CheckoutGentofteObjectsTestStep:Checkout the Gentofte objects]|| OK || || ||[:IngestObjectsTestStep:Ingest the objects]|| OK || || ||[:CheckResultsTestStep:Check the results]|| OK || Bug 234 was ignored in this test || |
||[[RunTestSetupTestStep|Run the test setup with blank install]]|| OK || || ||[[InstallIngestPackageTestStep|Install the ingest package]]|| OK || || ||[[CheckoutDOMSObjectsTestStep|Checkout the DOMS objects]]|| OK || || ||[[CheckoutGentofteObjectsTestStep|Checkout the Gentofte objects]]|| OK || || ||[[IngestObjectsTestStep|Ingest the objects]]|| OK || || ||[[CheckResultsTestStep|Check the results]]|| OK || Bug 234 was ignored in this test || |
| Line 54: | Line 54: |
| ||[:RunTestSetupTestStep:Run the test setup with blank install]|| OK || || ||[:InstallIngestPackageTestStep:Install the ingest package]|| OK || || ||[:CheckoutDOMSObjectsTestStep:Checkout the DOMS objects]|| OK || || ||[:CheckoutGentofteObjectsTestStep:Checkout the Gentofte objects]|| OK || || ||[:SabotageObjectsTestStep:Sabotage objects]|| OK || || ||[:IngestObjectsWithFailureTestStep:Ingest the objects]|| OK || || ||[:CheckIngestFailureTestStep:Check the failure output]|| OK || Bug 246 ignored in this test || |
||[[RunTestSetupTestStep|Run the test setup with blank install]]|| OK || || ||[[InstallIngestPackageTestStep|Install the ingest package]]|| OK || || ||[[CheckoutDOMSObjectsTestStep|Checkout the DOMS objects]]|| OK || || ||[[CheckoutGentofteObjectsTestStep|Checkout the Gentofte objects]]|| OK || || ||[[SabotageObjectsTestStep|Sabotage objects]]|| OK || || ||[[IngestObjectsWithFailureTestStep|Ingest the objects]]|| OK || || ||[[CheckIngestFailureTestStep|Check the failure output]]|| OK || Bug 246 ignored in this test || |
| Line 85: | Line 85: |
| ||[:RunTestSetupTestStep:Run the test setup with blank install]|| OK || || ||[:InstallIngestPackageTestStep:Install the ingest package]|| OK || || ||[:CheckoutDOMSObjectsTestStep:Checkout the DOMS objects]|| OK || || ||[:CheckoutGentofteObjectsTestStep:Checkout the Gentofte objects]|| OK || || ||[:SabotageFileStructureTestStep:Sabotage folder structure]|| OK || || ||[:IngestObjectsWithFailureTestStep:Ingest the objects]|| OK || || ||[:CheckDirectoryFailureTestStep:Check the failure output]|| OK || || |
||[[RunTestSetupTestStep|Run the test setup with blank install]]|| OK || || ||[[InstallIngestPackageTestStep|Install the ingest package]]|| OK || || ||[[CheckoutDOMSObjectsTestStep|Checkout the DOMS objects]]|| OK || || ||[[CheckoutGentofteObjectsTestStep|Checkout the Gentofte objects]]|| OK || || ||[[SabotageFileStructureTestStep|Sabotage folder structure]]|| OK || || ||[[IngestObjectsWithFailureTestStep|Ingest the objects]]|| OK || || ||[[CheckDirectoryFailureTestStep|Check the failure output]]|| OK || || |
| Line 119: | Line 119: |
| ||[:RunTestSetupTestStep:Run the test setup with blank install]|| OK || || ||[:StopFedoraIfItExists:Stop Fedora]|| OK || || ||[:InstallIngestPackageTestStep:Install the ingest package]|| OK || || ||[:CheckoutDOMSObjectsTestStep:Checkout the DOMS objects]|| OK || || ||[:CheckoutGentofteObjectsTestStep:Checkout the Gentofte objects]|| OK || || ||[:IngestObjectsWithFailureTestStep:Ingest the objects]|| OK || || ||[:CheckConnectionFailureResultsTestStep:Check the connection failure output]|| OK || || |
||[[RunTestSetupTestStep|Run the test setup with blank install]]|| OK || || ||[[StopFedoraIfItExists|Stop Fedora]]|| OK || || ||[[InstallIngestPackageTestStep|Install the ingest package]]|| OK || || ||[[CheckoutDOMSObjectsTestStep|Checkout the DOMS objects]]|| OK || || ||[[CheckoutGentofteObjectsTestStep|Checkout the Gentofte objects]]|| OK || || ||[[IngestObjectsWithFailureTestStep|Ingest the objects]]|| OK || || ||[[CheckConnectionFailureResultsTestStep|Check the connection failure output]]|| OK || || |
| Line 150: | Line 150: |
| ||[:RunTestSetupTestStep:Run the test setup with blank install]|| OK || || ||[:InstallIngestPackageTestStep:Install the ingest package]|| OK || || ||[:CheckoutDOMSObjectsTestStep:Checkout the DOMS objects]|| OK || || ||[:CheckoutGentofteObjectsTestStep:Checkout the Gentofte objects]|| OK || || ||[:IngestObjectsButKillFedoraWhileIngestingTestStep:Ingest the objects, but kill fedora while ingesting]|| OK || || ||[:CheckConnectionF0ailureTestStep:Check the connection failure output]|| OK || Test description changed to reflect the fact that all files are placed in failure/base at failure, no success directory is generated || |
||[[RunTestSetupTestStep|Run the test setup with blank install]]|| OK || || ||[[InstallIngestPackageTestStep|Install the ingest package]]|| OK || || ||[[CheckoutDOMSObjectsTestStep|Checkout the DOMS objects]]|| OK || || ||[[CheckoutGentofteObjectsTestStep|Checkout the Gentofte objects]]|| OK || || ||[[IngestObjectsButKillFedoraWhileIngestingTestStep|Ingest the objects, but kill fedora while ingesting]]|| OK || || ||[[CheckConnectionF0ailureTestStep|Check the connection failure output]]|| OK || Test description changed to reflect the fact that all files are placed in failure/base at failure, no success directory is generated || |
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.
Test step |
Status |
Notes |
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
Bug 234 was ignored in this 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.
Test step |
Status |
Notes |
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
Bug 246 ignored in this 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.
Test step |
Status |
Notes |
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
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.
Test step |
Status |
Notes |
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
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.
Test step |
Status |
Notes |
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
|
|
OK |
Test description changed to reflect the fact that all files are placed in failure/base at failure, no success directory is generated |