Integration Testing in [Unit Test View]

Background

CT provides several ways to design integration tests. While [Integration Test View] is commonly used, [Unit Test View] also provides feature to design and execute the same integration test scenarios.

Advantages of using [Unit Test View] for integration tests:

• Works similarly to [Integration Test View] adding test target functions.
• Allows consecutive execution of multiple functions in one test, reducing redundant tasks such as linking stubs.
• Debugging features available within [Unit Test View].
  

Designing and Running Integration Tests in [Unit Test View]

This guide explains how to design and run integration tests using a simple air conditioner example.

Define Integration Test Scenario

The source code and integration test scenario to be used as an example are as follows:

Example source code

void heating() { /* very complex code... */ }
void cooling() { /* very complex code... */ }
void fanOnly() { /* very complex code... */ }

typedef enum {
	OFF, COOLER, HEATER, FAN_ONLY
} Mode;
Mode mode = OFF;

void control_air_conditioner() {
    switch(mode) {
	case COOLER:
		cooling();
		break;
	case HEATER:
		heating();
		break;
	case FAN_ONLY:
		fanOnly();
		break;
	}
}

void initialize() {
	mode = FAN_ONLY;
	control_air_conditioner();
}

void setMode(Mode newMode) {
	mode = newMode;
}

Integration Test Scenario:

1. Call initialize() to perform initialization.
2. Call setMode() to change the mode to COOLER.
3. Call control_air_conditioner() to apply the setting.
4. Call setMode() to change the mode to HEATER.
5. Call control_air_conditioner() twice in a row to apply the setting.

Designing and Running the Test

Now, we will design the above scenario in [Unit Test View].

• Step 1: Determine Test Target Functions and Order
• Step 2: Create Unit Test
• Step 3: Configure Test Scenario
• Step 4: Enter Test Data
• Step 5: Maintain Test Case Context
• Step 6: Run the Test
  

Step 1: Determine Test Target Functions and Order

Determine the functions to call and their order according to the scenario:

Step 2: Create Unit Test

After determining the test target functions and their execution order in the previous step, proceed to create the corresponding unit tests. Choose the function that is either the first to be executed or the central one in the scenario. control_air_conditioner() is selected to create the unit test.

Step 3: Configure Test Scenario

1. Go to [Test Editor] > [Test Info Tab].
2. Add the functions to be called in [Test target function]. Use Ctrl + Click or Shift + Click to multi-select.
   
3. Use [Up]/[Down] buttons to arrange them in the defined order.
   
4. Where the same function is called multiple times like scenario 5. Apply air conditioner setting twice, adjust [Iteration count] for the test target function. In this case, set the [Iteration count] of the second control_air_conditioner() function to 2.
   
5. Save the test.

Step 4: Enter Test Data

1. Go to [Test Editor] > [Test Case Tab].
2. Enter parameters for the setMode(Mode) function according to the scenario.
   
   • For the first setMode(Mode) function, enter COOLER as the input value for the newMode parameter.
   • For the second setMode(Mode) function, enter HEATER as the input value for the newMode_1 parameter, and then save the changes.

*If there are many target functions, click the [Show as Tree] icon in the upper right of the [Test Case Tab] to make input easier based on the function call hierarchy.

Step 5: Maintain Test Case Context

In [Integration Test View], test cases are executed while maintaining context between them. To do the same in unit tests, go to [Test Editor] > [Configuration Tab] and check [Maintain test case context].

What is [Maintain test case context]?

By default, CT executes each test case independently without affecting others. The [Maintain Test Case Context] option changes this behavior. When enabled, the program state at the end of one test case is preserved and carried over to the next test case without re-initialization.
For example, when testing a function that increments a global variable a (initially 0) by 1:

• Context not maintained: a remains 1 after each test case
• Context maintained: a accumulates (1 → 2 → 3…) across test cases

Step 6: Run the Test

Click [Run Test] button to run the integration test scenario written as a single unit test. This unit test will behave the same way as the integration test shown below.

Conclusion

[Unit Test View] and [Integration Test View] each have their own characteristics.

Both views satisfy integration test requirements. Choose the appropriate method based on your testing purpose and structure.