TestCaseTelemetryManager_2 Class Reference
#include <TestCaseTelemetryManager_2.h>
Inheritance diagram for TestCaseTelemetryManager_2:
List of all members.
Detailed Description
Check the activation process of a telemetry manager.
A telemetry manager instance is created and configured as follows. As source of telemetry data, two dummy telemetry packets d1 and d2 are used. The two telemetry packets are encapsulated in two DC_DummyTelemetryPacket components and these are then loaded in a DC_SimpleTelemetryModeManager component. As telemetry stream, a DC_ByteArrayTelemetryStream component is used. The telemetry stream and the telemetry mode manager are loaded in the telemetry manager. The immediate dispatch queue of the telemetry manager is configured with a size equal to 2. The following tests are then performed:
-
The two telemetry packets are loaded and unloaded from the immediate dispatch queue and it is checked that the load and unload operations are correctly executed.
-
The correctness of the "full status" of the immediate dispatch queue is checked.
-
The telemetry manager is activated and it is checked that the values of the two telemetry packets d1 and d2 are correctly written to the telemetry stream.
-
The two telemetry items are loaded for immediate dispatch. The telemetry manager is activated again and it is checked that the values of the two telemetry packets d1 and d2 are written twice to the telemetry stream.
-
It is checked that the status of the telemetry items submitted for immediate dispatch has been changed to: "not in use".
-
The first telemetry packet is configured to return "data not valid". The telemetry manager is again activated and it is checked that only the second telemetry packet is written to the telemetry stream and that the correct event is generated to report the validity check failure.
-
The size of the telemetry stream is changed to accept only three bytes of telemetry data. The telemetry manager is again activated and it is checked that an event is generated to report the insufficient capacity of the telemetry stream.
-
The first telemetry packet is configured to report "data not valid" and it is submitted for immediate dispatch to the telemetry stream. The telemetry manager is activated and it is checked that the correct events are generated.
-
It is checked that the status of the telemetry item submitted for immediate dispatch has been changed to: "not in use".
-
The size of the telemetry stream is changed to be insufficient to accept the first telemetry packet. The telemetry packet is again submitted for direct dispatch to the telemetry stream and, after activation of the telemetry manager, it is checked that an event is generated to report the insufficient capacity of the telemetry stream.
-
It is checked that the status of the telemetry item submitted for immediate dispatch has been changed to: "not in use".
-
An attempt is made to submit three packets for immediate dispatch (the capacity of the immediate dispatch queue is 2) and it is checked that the correct event is generated.
- See also:
- CC_TelemetryManager
DC_SimpleTelemetryModeManager
DC_DummyTelemetryPacket
DC_ByteArrayTelemetryStream
- Author:
- Alessandro Pasetti (P&P Software GmbH)
- Version:
- 1.0
Definition at line 74 of file TestCaseTelemetryManager_2.h.
|
Public Member Functions |
|
| TestCaseTelemetryManager_2 (void) |
| | Set the identifier and the name of the test case to, respectively, ID_TELEMETRYMANAGER*10+1 and "TestCaseTelemetryManager_1".
|
| virtual void | runTestCase (void) |
| | Execute the test case.
|
Member Function Documentation
| void TestCaseTelemetryManager_2::runTestCase |
( |
void |
|
) |
[virtual] |
|
The documentation for this class was generated from the following files:
Copyright 2003 P&P Software GmbH - All Rights Reserved