Blog

A Step by Step guide to using the New HPE Virtual Table Server (VTS)
Introduction to the New HPE Virtual Table Server (VTS) – Part 1
Install and Setting up VTS – Part 2
Coding for VTS – Part 3
Advanced Topics in VTS – Part 4
Working with Tables
Sometimes working with VTS tables isn’t very straight forward.  VTS provides you with a single table for data sharing. Don’t think of it as a database table, think of it more of an Excel table.  There is NO forced row integrity – keeping related data on the same row Read Entire Entry

A Step by Step guide to using the New HPE Virtual Table Server (VTS)
Introduction to the New HPE Virtual Table Server (VTS) – Part 1
Install and Setting up VTS – Part 2
Coding for VTS – Part 3
Advanced Topics in VTS – Part 4 

NOTE:  You can have multiple instances of VTS running and being used during a test. These code samples are assuming you are using a single instance of VTS.  If you are using multiple instances, you’ll want to use the vtc functions and NOT the lrvtc functions!  Instances are c Read Entire Entry

A Step by Step guide to using the New HPE Virtual Table Server (VTS)
Introduction to the New HPE Virtual Table Server (VTS) – Part 1
Install and Setting up VTS – Part 2
Coding for VTS – Part 3
Advanced Topics in VTS – Part 4 
Install
This is the easy part.  You can find the VTS setup executable under the “Additional Components” folder in the LoadRunner install directory.  It is a quick and easy setup that you can do using the default options.  You can install the VTS on the same server as the co Read Entire Entry

A Step by Step guide to using the New HPE Virtual Table Server (VTS)
Introduction to the New HPE Virtual Table Server (VTS) – Part 1
Install and Setting up VTS – Part 2
Coding for VTS – Part 3
Advanced Topics in VTS – Part 4 For those of you who have been using LoadRunner for a while, you may have heard about the Virtual Table Server (VTS). This is a technology has been around since the early versions of LoadRunner. However, the original version of the tool was never officially supported by HPE. There was Read Entire Entry

Introduction to TruClient – Part 1
Recording in TruClient – Part 2 
Enhancing a TruClient Script – Part 3 

XPath

Objects can be identified several ways in TruClient.  The recommended way is to use Automatic whenever possible.  Unfortunately, this doesn’t always work.  One of the best solutions is to use XPath.  Under the Object sections you have the ID Method.  This is usually set to Automatic.  You can also change this to XPath, which allows you to see the XPath value or to JavaScript which allows you to Read Entire Entry

Introduction to TruClient – Part 1
Recording in TruClient – Part 2
Working with Objects, Variables, and Code in TruClient – Part 4 

Parameters

Define your parameters just like you normally would for an HTTP script.
There are several ways you can use parameters in a script.  The easiest way is to change the argument section of the step is to use the parameter from Plain to JavaScript.

Select the text you want to parameterize and right click it.  From the menu, you can create a new parameter or select from Read Entire Entry

Introduction to TruClient – Part 1
Enhancing a TruClient Script – Part 3
Working with Objects, Variables, and Code in TruClient – Part 4  

Recording in TruClient

First add a new script using the TruClient – Web protocol.  To record a script, you’ll need to select what browser you want to use.  On the toolbar, you’ll see a drop down next to the Develop Script button.  Select which browser you would like to use.  I suggest doing most of the scripting with Firefox since it seems to be the most mature of the TruClie Read Entire Entry

Recording in TruClient – Part 2
Enhancing a TruClient Script – Part 3
Working with Objects, Variables, and Code in TruClient – Part 4 

First, please don’t confuse TruClient with the Ajax – Click and Script protocol.  These are two totally different protocols based on completely different technology.  Click and Script was an early attempt at making a script that didn’t need traditional correlation.  It never was highly adopted and I don’t think it was well understood.  In version 11 of LoadRunner that all changed.  H Read Entire Entry

Previously we looked at using DFE to help make scripts that utilize XML to make it more readable and easier to parameterize.  There is another way to use DFE, beyond making a script more readable.  Sometimes DFE may be required for the script to run properly.  Some applications use what is called GWT (Google Web Toolkit).  To use GWT DFE, first you need to identify when an application is using GWT.

There is the obvious way that LoadRunner recognizes GWT.  You’ll see the following message in the Error tab of the messag Read Entire Entry

DFE is short for Data Format Extension.  It is a feature added to LoadRunner back in version 11, but a lot of people don’t understand what it is and how it can help you.  In simple terms DFE allows for easier LoadRunner scripting by allowing us to decode and encode normally unreadable or formatted data that the may be sent between the client and the server.  A simple example would be converting a long XML request into a more readable format.  Another example would be converting an unreadable Base 64 request into something that Read Entire Entry