User Steve Mathisen (email@example.com) posted:
If, by performance testing, you mean load or stress testing, then you are
Quality is the result of a carefully constructed cultural environment. It has to be the fabric of the organization, not part of the fabric.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by WinRunner: User Ran Nahman (firstname.lastname@example.org) posted:
FYI in the TSL help guide you can find two commands, start transaction and
These two functions are for interfacing with LoadRunner. You need a particular kind of LoadRunner virtual user called a gui virtual user. The list price for these is approx $1,500 / user. One user is good for invoking one WinRunner on a remote machine and launching a specified test with a specified gui map. The time differences between the start and end transactions are then sent back to load runner. The problem with start and end transaction is that there's no way to capture the transaction time within your testscript (although you can see it in your test results). You can simulate the start and end transaction functions in the following manner: