If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Re: Script execution timer?

Whatever is relative to performance measurements -
is not absolute time of Page loading or Transaction performed or any...
Timers of any kind [or Start\End Transaction] can be useful only informatively and will give some information after multiple running of the same scripts on the same Environment to compare them roughly.
There is lot of processes involved not to measured by Timers,
Because Timer doesn’t separate certain thread from them to measure it explicitly.

Re: Script execution timer?

[ QUOTE ]
Whatever is relative to performance measurements -
is not absolute time of Page loading or Transaction performed or any...
Timers of any kind [or Start\End Transaction] can be useful only informatively and will give some information after multiple running of the same scripts on the same Environment to compare them roughly.
There is lot of processes involved not to measured by Timers,
Because Timer doesn’t separate certain thread from them to measure it explicitly.

Janna

[/ QUOTE ]

Does this mean that we shouldn't even bother using this as a form of performance testing? I know for a fact that our company won't pay for LoadRunner so I am looking for a poor man's version.

Re: Script execution timer?

If you are using the "Transaction Timer" of QTP to do Performance testing, then you are headed in the wrong direction. As far as I know, these "transaction timers" will measure the script run time and not the performance of application.

Re: Script execution timer?

[ QUOTE ]
If you are using the "Transaction Timer" of QTP to do Performance testing, then you are headed in the wrong direction. As far as I know, these "transaction timers" will measure the script run time and not the performance of application.

Re: Script execution timer?

&gt;Does this mean that we shouldn't even bother using this as a form of performance testing?&lt;

NO, No, NO...
Not at all !
I did not say that we should not use Timers totally.
As opposite: we SHOULD. And we use them.
I myself use different Timers for rough routines measurement.

What I'm trying to say is:
we have to understand nature of those Timers. That's it.
We can not name it: Performance testing of Page Loading and
give those Result numbers to the client or to Management as final performance statement to make some kind of resolution.
But, using Timers build by build, run by run - you'll gather enough information to compare and can say for sure,
for example:
"this build is slower then previous, but faster then 3-4 builds ago"...
OR
"With this DataBase - page loading much faster, then with other"...
OR
On "WinXPsp2 it works slower then on Vista"...
Something like that.

And it will be absolutely correct statements, based on your every run measurements.
In this case: it doesn't matter how many processes or threads, or additional components were involved.
Matter is:
EVERY TIME estimation was done IDENTICALLY by your script, you have the numbers to show and compare and you and anybody can analyze your numbers.
Any judgment, based on such an understanding - will be absolutely correct and useful.