How do I set up transactions to measure response times?

I am running an AppLoader test and I want to know how long specific tasks in my scenario take. This is done by adding Transaction actions to your scenario. This article provides details on how to do this.

ScenarioBuilder has automatic response time reporting at the Scenario and Component levels. To isolate and report on specific events within these levels, simply tag a step or series of steps with Begin and End “Transaction” actions. ScenarioBuilder will include Transaction response times in all reports and graphs. You can even nest transaction timing. Here is an example.

In this example we have a scenario that performs the following:

  1. Logs into the app
  2. Navigates to patient records
  3. Searches for a specific patient
  4. Launches the patient and edits information
  5. Saves the changes
  6. Returns to the patient records dashboard

When I execute this scenario I will automatically get timing information on how long it takes to do all 6 processes. In addition to that, I need to know the following timing information:

  • Time to log in (login)
  • Time to reach patient records dashboard (dashboard launch)
  • Time to complete search (search)
  • Time to search for the patient, bring up the record, make edits and save it (edit record)

I can obtain this timing information by adding Begin Transaction and End Transaction actions to the script. When adding a Begin Transaction action you give the transaction a name. Then when adding the End Transaction action you select the Begin Transaction you want to end by selecting it from the drop-down. In our scenario it would look like this.

Begin Transaction - login

1. Logs into the app

End Transaction - login

Begin Transaction - dashboard launch

2. Navigates to patient records

End Transaction - dashboard launch

Begin Transaction - edit record

Begin Transaction - search

3. Searches for a specific patient

End Transaction - search

4. Launches the patient and edits information

5. Saves the changes

End Transaction - edit record

6. Returns to the patient records dashboard

So remember to use Transactions for that extra layer of reporting so you can get to the bottom of your performance issues.