Version: v3.0Beta1/2005-04-19T16:07:03
Test Suite: ngamsArchiveCmdTest
Description:
Synopsis:
Test the ARCHIVE Command.
Description:
The Test Suite exercises the ARCHIVE Command. It tests the normal behavior,
but also more advanced features such as Back-Log Buffering.
Both Archive Push and Archive Pull is tested.
The Archiving Proxy Mode/Archiving Multiplexing is also tested.
Missing Test Cases:
- Tests with 'real file systems' (simulated disks).
- Test Back-Log Buffering for all defined cases:
o NGAMS_ER_PROB_STAGING_AREA
o NGAMS_ER_PROB_BACK_LOG_BUF
o NGAMS_AL_MV_FILE
- M=R/Synch: Check that they are declared as completed
simultaneously + Disk Change Email Messages sent out.
- M1s.
- Check that back-log buffered file properly archived.
- Check that back-log buffered + pickle files removed.
Such a test would replace: test_BackLogBuf_1/2 (check).
- Implement test in ngasPlugIns/test to test the external plug-ins.
The NG/AMS Test Framework can be used. Tests are:
- Archiving of Tar-balls
- ngasGarArchFitsDapi.py
- Other plug-ins.
Test Case: test_ArchiveProxyMode_01
Description:
Synopsis:
Test Archiving Proxy Mode - 1 Master/no archiving, 4 NAUs.
Description:
The purpose of this Test Case is to test that the Archving Proxy Mode
works as expected.
One master node is configured to archive onto four sub-nodes. The
master node itself does not support archiving.
It is checked that within a limited number of archive attempt, the
file is archived onto all nodes.
Expected Result:
After having configured and started the servers, a test file will
be archived up to 100 times. It should within these 100 attempts, be
archived onto all archiving units.
Test Steps:
- Start master node configured to archive onto 4 NAUs.
- Start four NAUs.
- Archive a small file to the master until it has been archived
onto all NAUs. Max tries: 100.
Remarks:
...
Test Data:
...
Test Case: test_ArchiveProxyMode_02
Description:
Synopsis:
Test Archiving Proxy Mode - 1 Master/+archiving, 3 nodes.
Description:
The purpose of this Test Case is to test that the Archving Proxy Mode
works as expected.
One master node is configured to archive onto three sub-nodes. The
master node itself supports archiving.
It is checked that within a limited number of archive attempt, the
file is archived onto all nodes.
Expected Result:
After having configured and started the servers, a test file will
be archived up to 100 times. It should within these 100 attempts, be
archived onto all archiving units.
Test Steps:
- Start master node configured to archive onto 3 NAUs + having
own storage sets.
- Start three NAUs.
- Archive a small file to the master until it has been archived
onto all NAUs + the master. Max tries: 100.
Remarks:
...
Test Data:
...
Test Case: test_ArchiveProxyMode_03
Description:
Synopsis:
Test Archiving Proxy Mode - 1 node no sto. sets, 1 node Offline.
Description:
The is virtually the same as test_ArchiveProxyMode_01(). However,
in this test, one NAU has no free Storage Sets and another is
Offline.
Expected Result:
After having configured and started the servers, a test file will
be archived up to 100 times. It should within these 100 attempts, be
archived onto the available archiving units.
Test Steps:
- Start master node configured to archive onto 4 NAUs.
- Start four NAUs.
- Set all disks for one unit to completed with an SQL query.
- Bring one unit Offline.
- Archive a small file to the master until it has been archived
onto all available NAUs. Max tries: 100.
Remarks:
...
Test Data:
...