Creating a Login Schema

A login schema defines how to log in to an SUT at recording and execution time. You create them depending on the executable type of a test script. For more information, see Executable Types.

TCE supports login schemas for the following executable object types:

URL.
Long URL (containing more than 255 characters)

A login schema contains a list of Unified Resource Identifiers (URIs). A URI identifies uniquely a UI control on a page, so the login schema defines which UI controls are to be used to log in.

There are three mandatory URIs to be defined for the:

Entry field for the user name
Entry field for the password
Pushbutton or link to activate the validation of the credentials

Prerequisites

You are editing a CBTA-based test configuration, the executable type is URL.

Procedure

Caution Caution

Ensure that you use only non-production users and non-production systems.

End of the caution.

Note Note

Do not use a login schema in a test script if its test profile refers to an SUT for which you have configured anonymous URI-based SUT access. For more information, see Creating a Test Profile With Logon Data for SUTs.

End of the note.

Open the logon page of the application to be tested.
On the Attributes tab page, under Additional Test Options, choose the Login Schema F4-Help.

A dialog box appears.
Choose the Create pushbutton.
The Login Schema Creation Wizard is displayed.
Enter data as required.
In the Login Schema Wizard, choose the Refresh Sessions pushbutton.
In the list of available sessions, select the session corresponding to the logon page.
Specify the URIs of the logon page to which you want to assign values:
1. Position the mouse on an objects, click it, and go back to the Login Schema Creation Wizard.
2. Choose the Spy pushbutton.
3. Enter the value.
Specify the following URIs:
- Input field for the user name
- Input field for the password
- Confirmation pushbutton
You can define up to four additional URIs. When such an optional URI is defined, the system identifies the corresponding type of control and performs the corresponding action accordingly. For example, if the additional URI identifies a checkbox, then this checkbox is selected. These four optional URIs are executed after the login pushbutton is pushed. This is useful if additional pop ups or messages are to be confirmed.

You can also select an entry field to enter the language code.
Choose Next.

The login schema is uploaded to the SAP Solution Manager system.
Select a transport package, and save your entries.
Go back to the Login Schema Creation Wizard window.
The status is green.
Choose Finish.

Result

The login schema can be selected in the corresponding field when defining an executable in TCE. For more information, see Executable Types.

At recording and execution time, the login schema file is downloaded to the front-end environment, next to the CBASE files. It is then used at login time.

Login schema definition files (with the .lsd extension) are stored centrally in the SAP Solution Manager and synchronized automatically on all front end machines that use CBTA. It is stored in the mime repository, next to the CBASE files. If your user has the S_DEVELOP role, you can display them in transaction SE80, under SAP/PUBLIC/CBTA/LOGIN_SCHEMA.