About Systems Under Test


The System Under Test (SUT), also referred to as a Device Under Test (DUT), is a specific piece of equipment that will be sent control and bearer traffic from the test servers in the course of a test session. A test case is designed to test a specific type of SUT, as shown in the test case configuration diagrams. In an end-to-end test configuration, two or more SUTs are used in the test. In a nodal configuration one SUT is used. A test system can have up to 512 defined SUTs.

As part of defining a test case, you will be asked to choose the SUT(s) that will be used in the test from a drop-down list. This list is compiled from the SUTs that are defined in the database. When you define an SUT, you provide the information necessary for the test system to communicate with the device. This ensures that test cases are always using the current communication settings.

TIP: The type of testing that you normally perform can suggest a strategy for choosing SUT Names and Types.

  • If your SUT list will be static — the same devices are dedicated to testing and configured for particular uses — include the use in the SUT Name. This will make it easier for the testers to choose which SUT is appropriate for their test.

  • If your SUT list will be dynamic — devices will come and go — define "generic" SUTs by type and include the type and the address in the SUT Name. When a new device is placed in the test environment, either configure it according to the SUT definition or modify the SUT definition to accommodate the device. In this way, you can maintain a reusable set of tests that will not have to be modified because the assigned SUT no longer exists in the system.

With the System Under Test Administration window System and Test Administrators can:

NOTE: The System Under Test Administration window displays in three modes: Add, Edit, and View.

System Under Test Administration is also supported by :

NOTE: All users can view the SUT properties in View mode and connect to the SUT.


 

Related Topics

  1. About Test Cases
  2. Deployment Guidelines