Framework Testing

• At component level in the desktop environment
• At system level in the desktop environment
• At component level in the embedded environment
• At system level in the embedded environment

• Back to Real-Time Java Project Home

Component-Level Testing in Desktop Environment

public abstract class TestCase {

  . . .

  TestCase(int testId, string testName);

  // To be called before the test starts. Returns false if
  // initialization failed
  public boolean setUpTestCase();

  // To be called to execute the test
  public abstract void runTestCase();

  // To be called after test execution. Returns false if
  // shut down failed
  public boolean shutDownTestCase();

  // Set the test result -- can only be called once!
  public void setTestResult(bool outcome, string failureMessage);
  . . .

};

Test cases are completely self-contained and independent from each other. For each test case, a subclass of TestCase is created. Since most of the framework test cases require the same set up actions to be performed before the test execution begins, a class TestCaseGenericSetUp is provided to perform this common initialization actions and to serve as a convenient base class from which to derive specific test case classes.

The framework defines a large number of test cases that test various aspects of key components. The test case classes are called TestCaseXxx where 'xxx' is either the name of the component to be tested or of the framelet to which the component(s) to be tested belong.

Sequences of test cases can be loaded into a test suite. A test suite allows several test cases to be executed in sequence as a single unit. Test suites are encapsulated in instances of the following class:

public class TestSuite {

  . . .

  // Defines the file to which the test results are sent
  TestSuite(PrintWriter outputFile);

  // Execute all test cases in the test suite
  void runTestSuite();

  // Load a test case in the test suite
  void loadTestCase(TestCase newTestCase);

};

The desktop version of the framework defines a single project called RegressionTest that executes all the test cases predefined by the framework in sequence. This project can be used to perform regression testing on the framework.

Back To Top, Back to Real-Time Java Project Home

System-Level Testing in Desktop Environment

• the unit components (classes AnalogSensor and AnalogActuator) are replaced with two test unit components (classes TestAnalogSensor and TestAnalogActuator). The test sensor simulates a sensor that acquires a fixed value (which is hardcoded in the sensor class code). The test actuator sensor writes its output data to the standard output.
• the AOCS clock component (class JbedSmmClock) is replaced with a test clock component (class TestSmmClock) that retrieves time information using Java's standard System.currentTimeMillis service).

Instantiation of the test SMM application uses the same same instantiation factories as the prototype SMM application with the following exceptions:

• factory JbedSmmSystemFactory is replaces with TestSmmSystemFactory to generate the test version of the AOCS clock
• factory JbedSmmUnitFactory is replaced with TestSmmUnitFactory to generate the test versions of the units

The prototype instantiator component JbedSmmInstantiator is replaced with an instantiator component TestSmmInstantiator that is identical to the former except that it uses the test versions of the system and unit factories.

Note that, since telemetry and telecommand data in the prototype application are sent and received through TCP/IP, the same code works in the desktop environment and therefore there is no need to replace the telecommand and telemetry components. As a further consequence, the same ground station simulator can be used both for the prototype and for the test applications. 

The scheduling policy adopted for the test application is the same as for the prototype application. However, since the run-time system in a desktop environment has different characteristics from the Jbed run-time system, application behaviour is not exactly reproducible. The test application is used primarily to verify the functional correctness of the application code. No simulator of the SMM system is available and therefore the tests are performed in open-loop mode.

Back To Top, Back to Real-Time Java Project Home

Component-Level Testing in Embedded Environment

Back To Top, Back to Real-Time Java Project Home

System-Level Testing in Embedded Environment

Back To Top, Back to Real-Time Java Project Home