Default language.

Step 2: Define Interface


The basic definition of an interface is the name of the program to be called (referred to as the test target) and the data structures passed to it as call arguments. This corresponds to the technical interface as specified in a CALL statement (program name and USING parameters). 

The technical interface is completed by adding the type of usage of the structures and/or attributes within them. The usage is:

  • Usually a convention between caller and called program on which structures or attributes are used as input data or output data.
  • Other types of usage are: fixed technical data, or no usage at all (for details see Usage for Structures and or Attributes).

We recommend that you perform this step thoroughly, because it increases the efficiency of creating test scenarios.

  1. Right-click on your  project Interfaces folder, then from the context menu, select New > image2022-11-8_15-40-23.png Unit Test Interface.
    (alternatively, from the menu, select File > New > Other > BMC >  > image2022-11-8_15-40-14.png Unit Test Interface.
    The New  Interface Wizard opens.
  2. Enter Name, Alias name, Type, and Description, then click Next >.
  3. Add the required call parameters (structures) for this program by moving the desired items from the Available to the Selected column.
  4. Click Finish.
    The Interface Editor opens with the newly created interface.
  5. Select usage for structures and/or attributes.

Usage for Structures and/or Attributes

Usage

Meaning

Visibility in Test Scenario Editor

in

Used as input data

In Input Data

out

Used as output data

In Simple Check Conditions

inout

Used as input and output data as well

Both in Input Data and Simple Check Conditions

fix

Fixed (technical) data, contents set in the interface only

No

none

Not used and never filled with any dataA

No

 For details on Usage none, see Edit Parameters.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*