About Test Cases
A test case contains the parameters required to define a test that will be executed on a configuration of Systems Under Test (SUTs) in a specific type of network. When the test case is executed, the parameters are used to configure the test server modules that perform the test.
In general, a test case is comprised of:
-
Test control parameters that define the global boundaries of the test — the rates and volume of control traffic
-
The functional aspect of the test case — the test activity — which can contain its own set of rate, volume, and protocol definitions
-
Emulator definitions for the simulated devices included in the test
-
Definitions for the protocols that are used in the test
-
The protocol, rate, and volume definitions for the bearer traffic (data traffic) that can be added to the test
-
The definition for a query that can be periodically sent to the SUT during the test
|
NOTE: All options are not applicable to all test cases. |
A test case is configured using the Test Case Settings window..., which displays the parameters available in the test case. The parameters are arranged in groups on tabbed panes. The test case draws on the TAS database for the information needed to communicate with the SUT and with the test servers in the system. The tabs and parameters that are available in any given situation depend on the test case and the options selected in the definition. Tabs and parameters are dynamically added or removed as you choose to enable or disable the protocols or other options to be used in the test.
Test Activities
Every test case uses a functional activity to test the performance or capacity of the SUT. A set of test activities is built in to the test system, and can be used in any test case that is appropriate for the activity.
Test Options
You can add optional components to further test an SUT's capacity and monitor its performance. The basic options listed below are available in most test applications. Other options may be available depending on the test application.
-
Data Traffic — A variety of data types can be used to generate bearer traffic during the test. The test system provides a variety of data protocols to choose from, and the data traffic parameters provide the flexibility to shape the traffic by defining the packet sizes and transmission rates.
-
SUT Query — You can use the SUT query option to monitor the CPU usage during the test and even dynamically adjust the control traffic rates until the desired CPU threshold is reached.
Using Test Cases
A set of test case templates is provided in the Test Library of your system. These predefined test cases can be modified by configuring the parameters as needed to achieve the goal of that test case. You can save the configured test case in another section of the Test Library for use in other test sessions, or save the test case definition as part of the test session.