Show TOC

Procedure documentationCreating a Login Schema

 

A login schema defines how to log in to an SUT when automating web scenarios (URL executable object type), at recording and execution time.

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

A login schema contains three parts: pre-login steps, login steps and post-login steps:

  • Pre-login steps

    This part performs mandatory actions before entering the user name and the password. You can define as many actions as required.

  • Login steps

    In the main part of a login schema, three mandatory URIs are 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

    If the login screen contains other fields (to specify the language, for example), you can define additional URIs, Such actions are performed before the user credentials are confirmed.

  • Post-login steps

    If some steps are to be performed after the login button has been pressed, you can define post-login actions. You can define as many actions as required.

Each part contains a number of actions. An action is defined by an URI and an optional value.

Prerequisites

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

Procedure

Caution Caution

Only use non-production users and systems.

End of the caution.

Note Note

Do not use a login schema in a test script if it's 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.

  1. Open the logon page of the application to be tested.

  2. On the Attributes tab page, under Additional Test Options, choose the Login Schema F4-Help.

    A dialog box appears.Existing login schemas found in the MIME repository are displayed.

    By default, CBTA provides a login schema NW_STANDARD_LOGON which you can used to record and execute test scripts on SAP NetWeaver Java systems (version 7.01 or higher).

  3. Choose the Create pushbutton.

    The Login Schema Creation Wizard is displayed.

  4. Enter data as required.

    If you enter the name of an existing login schema, a counter suffix is added by default. To overwrite an existing login schema, choose the Overwrite existing login schema field.

  5. In the Login Schema Wizard, choose the Refresh pushbutton.

  6. In the list of available sessions, select the session corresponding to the logon page of the tested application.

  7. Specify the URIs of the logon page:

    1. Choose the Spy pushbutton of the field you want to identify, for example the user name field.

    2. Switch to the logon page of the tested application.

    3. On the logon page, position the mouse on an object (in our example, the user name field).

      UI elements under the mouse are be highlighted. If UI elements are not highlighted correctly, check the zoom factor in Internet Explorer which must be 100%.

    4. Click the object you want to identify (the user name field, in our example).

    5. Go back to the Login Schema Creation Wizard.

      The URI of the selected UI element is displayed in the corresponding field.

    6. Repeat the previous step for all UI elements to be specified. The following fields are mandatory:

      • Input field for the user name

      • Input field for the password

      • Confirmation pushbutton

    To specify additional fields (a field to set the language, for example), define additional login steps. To specify the value, choose the With value field.

    Note Note

    For the user name field and the password field, the With value fields are disabled since the user name and password are automatically retrieved from the SUT management.

    End of the note.

  8. Define pre-login and post-logon steps, if required.

    Pre-login steps are performed before entering the user credentials. Post-login steps are performed after the user credentials are confirmed.

  9. Choose Next.

    The login schema is uploaded to the MIME repository of the SAP Solution Manager system.

    The Object Directory Entry Creation dialog box appears.

    If the dialog box is not visible in the Windows task bar or if the wizard seems to be blocked on the upload step, minimize all others applications, to display the dialog box.

  10. Select a transport package, and save your entries.

  11. Go back to the Login Schema Creation Wizard window.

    The status is green.

  12. Choose Finish.

Result

The login schema can be selected in the corresponding field when defining the test script attributes in the TCE.

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.