Task: Identify Test Cases for Systems Integration
This task describes how to identify the test cases for systems testing.
Relationships
RolesPrimary: Additional: Assisting:
InputsMandatory: Optional: External:
  • None
Outputs
Main Description

Define test context

The first step in performing System Integration test is to define what will be tested, the System Under Test (SUT). Many times, the SUT will encompass the complete system. In other cases, it will encompass a subset of subsystem/components that interact together to meet some capability. Often, System Integration testing requires that the tests run on the target device or a simulator. This environment restriction requires a special software build with all required components. If all required parts are not available, it may be possible to use a simulator or build special testing components for a subsystem.

Define test cases

Identify test cases by identifying the functionality you are building. Each test case defines a specific capability. This functionality may be described by a use case, an activity diagram or flow chart, a state chart, or a set of requirements. For each test case, define one or more test scripts so that the capability is fully exercised. It is important to specify the scenario completely, including exception handling conditions.