Executable Types

Assign the executable which corresponds to the application to be tested. Define the executable type and the executable.

For more information assigning one of the Web executable types mentioned below, see “CBTA 3.0 SP02 – Web Executable Objects” (http://service.sap.com/~sapidb/011000358700000195312014E.PDF) on SAP Service Marketplace at http://service.sap.com/testing Media Library Test Management .

Executable Type available in the Test Composition Environment

The executable type describes the UI technology used by the application to be tested, for example, Transaction. or CRM Web Client Application.

If you use CBTA, you have the following options:

BMTA – Transaction: SAP GUI technology. The system under test is an SAP ABAP system accessed via an RFC destination. Select an executable depending on the SAP Solution Manager context you have defined.
In the Executable field, enter the transaction code, for example SU01.

The interfaces of transactions or function modules are imported automatically from the SAP Solution Manager system landscape, if a system data container was assigned to the test case and an SAP Solution Manager project or solution and a system role were assigned to the test case.
BSP_APPLICATION – Business Server Pages application: This is a web-based UI technology. The system under test is an SAP ABAP system accessed via an RFC destination.
In the Executable field, enter the name of the BSP application.

You can define additional parameters, according to the following schema: my_bsp_application?param1=value1&param2=value2&param3=value3.

Example
To test http://sq7.wdf.sap.corp:50089/sap/bc/bsp/sap/sbspext_htmlb?sap-client=200, enter sap/sbspext_htmlb?sap-client=200.

End of the example.
CRM_WEBCLIENT – CRM Web Client application: This is a web-based UI technology. The system under test is an SAP ABAP system accessed via an RFC destination.
In the Executable field, specify the SAP role and logical link according to the following pattern: saprole=<ROLE>&crm-logical-link=<logical link>.

Example
saprole=AIC_MANAGER&crm-logical-link=ACO-DIS-ED

End of the example.
URL – Web address or file: This is a web-based UI technology. The system under test can be:
- An SAP ABAP system for Web GUI UI technology
- An SAP Java system for SAP Portal
- A server for Web (Internet/Intranet) UI technology (HTML, SAP UI5)
Do the following:
1. In the Executable field, enter one of the following:
  - A relative URL.
    
    Note
    The base URL must be defined in the test profile. For more information, see Creating a Test Profile With Logon Data for SUTs.
    
    End of the note.
  - An absolute URL. The target component and test profile do not alter the URL. For more information, see Creating a Test Profile With Logon Data for SUTs.
2. To allow the system to retrieve the user credentials (or anonymous flag), select a test profile. For more information, see Creating a Test Profile With Logon Data for SUTs.
3. Select a login schema. Enter one of the following:
  - SAP Portal: NW_STANDARD_LOGON
  - Web GUI: ABAP_TAF_LOGON
  - Third-party web server: If authentication is required, enter the name of a custom login schema. If no authorization is required, leave the field empty.
    For more information, see Creating a Login Schema.
WDY_APPLICATION – Web Dynpro application: This is a web-based UI technology. The system under test is an SAP ABAP system accessed via an RFC destination.
In the Executable field, select a Web Dynpro ABAP application name.

Certain applications require additional parameters. They can be defined according to the following schema:0E/namespace/my_wda_application?param1=value1&param2=value2&param3=value3.

An application name has one of the following prefixes:
- 0E: HTTP protocol
- SE: HTTPS protocol
To find the parameters required by the application, see the address bar of your web browser when using the tested application (usually started manually).

Caution
Do not reuse the session ID and SAP client parameters. On loading the application page, the system recalculates them.

End of the caution.

Example
0E/SAPSRM/WDA_L_FPM_OIF?WDCONFIGURATIONID=/SAPSRM/WDAC_I_FPM_OIF_SC_PROF=CREATE=BUS2121=SC_PROFESSIONAL_PURCHASER

End of the example.
WDY_JAVA_SOLMAN – Java Web Dynpro application: This is a web-based UI technology. The system under test is an SAP Java system accessed via a URL.
Do the following:
1. In the Executable field, enter a Java Web Dynpro application name.
  You can define additional parameters, according to the following schema: my_jwd_application?param1=value1&param2=value2&param3=value3.
  
  Example
  To test http://sq7.wdf.sap.corp:58900/webdynpro/dispatcher/sap.com/tc~smd~server~agent~admin/Support, enter sap.com/tc~smd~server~agent~admin/Support.
  
  End of the example.
2. To allow the system to retrieve the user credentials (or anonymous flag), select a test profile. For more information, see Creating a Test Profile With Logon Data for SUTs.
3. Select a standard login schema or create a custom login schema via the F4 help.
  Depending on the UI technology, you can select one of the following standard login schemas:
  - SAP Portal: NW_STANDARD_LOGON
  - Web GUI: ABAP_TAF_LOGON
  For more information about creating a custom login schema, see Creating a Login Schema.

Additional executable types available for the Business Blueprint test cases

If you come from the Business Blueprint (transaction SOLAR02), the following additional executable types are supported:

LONG_URL: Executable type supporting the same UI technologies and system under tests as the URL type. This type is required only if you create the test configuration in transaction SOLAR02 and if the URL has more than 255 characters.

Recommendation
To ensure maximum performance, use the URL executable type, if the URL has less than 255 characters.

End of the recommendation.

Do the following:
1. In the Executable field, enter one of the following:
  - A relative URL. The base URL is taken from the target component or the test profile.
    For more information about the test profile, see Creating a Test Profile With Logon Data for SUTs.
  - An absolute URL.
    The target component and the test profile do not alter the URL. For more information, see Creating a Test Profile With Logon Data for SUTs.
2. To allow the system to retrieve the user credentials (or anonymous flag), select a test profile. For more information, see Creating a Test Profile With Logon Data for SUTs.
3. Select a login schema. Enter one of the following:
  - SAP Portal: NW_STANDARD_LOGON
  - Web GUI: ABAP_TAF_LOGON
  - Third-party web server: If authentication is required, enter the name of a custom login schema. If no authorization is required, leave the field empty.
    For more information, see Creating a Login Schema.
Note
If neither an SDC nor a target component are defined, neither a test profile nor a login schema can be found. In this case, the anonymous logon is used, depending on the system.

End of the note.

Note Note

A default login schema is used if no value is selected in the Login Schema entry field. This default login schema is used for HTML-based UI Technologies on an SAP ABAP system.

End of the note.