Case study A: Recording and replaying with no adjustment

To record a transaction sequence

1. Start the KITE 4.0 application.

2. On the Script tab, click Record. 

   By default, the record dialog box opens to Record Internet Explorer | Firefox Script (TxP).

   If you do not want any cookies on your system to be available to the script start site, do not clear the Record as a new visitor check box.

   To change the record option, click the down arrow under the Record button, and select a record option. 

3. Enter the Mid TierURL in the Starting URL dialog box.
4. To start recording, click OK.
   KITE opens the Mid TierURL and records the action as Action 1 in Script Viewer.

5. In the test browser, select No from the pulldown option for Dynamic New Page.

   Select No to keep the new navigation and network activity within the current KITE action. For more details about using Dynamic New Page options, see the KITE 4.0 help documentation.

6. Enter your AR Systemcredentials and log in.
   A successful login action marks the completion of Action 1 in Script Viewer.

   At this point, the Script Viewer does not reflect the page completion for Action 2. Page completion is recorded when the next action is taken.

7. From the browser, select the Incident Management Console.
   This selection is recorded in the Script Viewer, by the start of Action 3, click on SPAN.
8. From the Incident Management Page, click anywhere on the screen to record the completion of Action 3.
9. To end the transaction record, log out of the Mid Tier.
10. To complete Action 4, click Stop. 
    The transaction is recorded and ready for replay.

To replay a recorded transaction

1. Click Play in Internet Explorer.

2. Select Yes to save changes dialog to the new script, then follow the on-screen prompts to save the created script.

   For this case study, the script is named Login_Open-Incident-Console_Logout.krs.

3. Observe the replay actions based on the created script.

   The green entries in Script Viewer indicate that the KITE script ran successfully. Failures are indicated by the color pink in the Script Viewer.
   The KITE replay indicates that Action 1 through Action 4 are completed successfully.

   
   
   At this point, the KITE application processes the test and displays measurement results.

Transaction Performance Summary

The Transaction Performance Summary for case study A displays the following values:

• Network Time
• User Experience Time
• Download Size
• Downloaded Page Elements
• Page Elements Errors
• Custom Components
• Cached Performance

The Show Performance Summary Dialog window can be closed, or turned on or off.

Transaction Events Log

The Transaction Events Log for case study A captures the HTTP traffic that occurs during a script replay.