Record transaction breakdown information

VuGen provides a diagnostic tool for understanding the transaction components in your test—transaction breakdown. Using transaction breakdown, you can determine where the bottlenecks are and the issues that need to be resolved.

When preparing your script for transaction breakdown, we recommend that you add think time steps at the end of each transaction using the ratio of one second per hour of testing. For more information about adding think time steps, see Insert steps into a script.

In order to record the transaction breakdown information, you need to modify your the parameterization functions in your script.

Prepare your script for transaction breakdown

  1. Identify the script parameterization replacement of the Session ID.

     /* Registering parameter(s) from source task id 15
        // {Siebel_sn_body4} = "28eMu9uzkn.YGFFevN1FdrCfCCOc8c_"
        // */
  2. Mark the next web_submit_data function as a transaction by enclosing it with lr_start_transaction and lr_end_transaction functions.

  3. Before the end of the transactions, add a call to lr_transaction_instance_add_info, where the first parameter, 0 is mandatory and the session ID has a SSQLBD prefix.

            "Name=SWEUserName", "Value=wrun", ENDITEM,
            "Name=SWEPassword", "Value=wrun", ENDITEM,
            "Name=SWERememberUser", "Value=Yes", ENDITEM,
            "Name=SWENeedContext", "Value=false", ENDITEM,
            "Name=SWEFo", "Value=SWEEntryForm", ENDITEM,
            "Name=SWETS", "Value={SiebelTimeStamp}", ENDITEM,
            "Name=SWECmd", "Value=ExecuteLogin", ENDITEM,
            "Name=SWEBID", "Value=-1", ENDITEM,
            "Name=SWEC", "Value=0", ENDITEM,
    lr_end_transaction("LoginSQLSync", LR_AUTO);

    Note: To avoid session ID conflicts, make sure that the Vusers log off from the database at the end of each session.

Back to top