Easy way to automate testing: 2008-02

Have you noticed, that HP Knowledge Base contains a new version of LoadRunner - 9.10?
Here it is:

For the present day (Feb 29th, 2008) HP LoadRunner 9.1 (9.10) is not published yet for downloading.
So, we have to wait for HP LoadRunner 9.1 (9.10) release or beta announcement...

Well, what's new in the future LoadRunner?
Please, see excerpts from HP LoadRunner 9.1 'What's new' file:

Version 9.1 expands support for Web 2.0 applications by adding protocol support for Adobe’s popular AMF flash. This, alongside existing support for AJAX makes LoadRunner the solution of choice for Web 2.0 performance validation.

In addition, LoadRunner 9.1 has enhanced testing capabilities for SOA and web services, as well as improved reporting for SOA performance metrics.

Version 9.1 also adds support for Microsoft RDP, Vista, and VMWare powered platforms.

Features are very interesting and appetizing! :)
When I have a possibility to download LoadRunner 9.1 (9.10) and evaluate it, I'ii share my impressions, dear readers.

--
Best regards,
Dmitry Motevich

I continue explaning about LoadRunner iteration number.
Well, how to determine the current iteration number?

The first way is to use LoadRunner parameter od 'Iteration Number' type.
It is described here
The second way is to use a LoadRunner global variable.
I will explain this approach now. Also, you will see how to define and use global variables.

Define a global variable
You can add a new variable definition into vuser_init section of LoadRunner script:
Then we will add a variable incrementation and usage into Action section of LoadRunner script. For example, like this:
Please, note that LoadRunner does not require using of "extern" keyword.
And last step is to open LoadRunner Run-time Settings and to set the desired total iteration count. In my example I set it to 3:
That's all! Let's start our script and see Log-file:

As you can see, nIterationNumber variable changes its values with every new iteration.

Tip: do not forget to increment its value, for example with ++ operator.

Both proposed approaches (with LoadRunner parameter and with a global variable) are simple enough. Use any you like and track your LoadRunner iterations thoroughly :)