Skip to main content

How to avoid think time / wait time from being accumulated in Custom Timers.

In Silk Performer custom Timers are used to generate response time around
transactions. It is usually inserted in the script generated by SP recorder. In
a typical script it looks as following -

==========================================================
MeasureStart("1020_ RANK_PREFERENCE"); // Custom Timer - Start for Rank
Prefpage

WebUrl("https://test-qa.test.edu/testtesting/images/arrow.png");
**** Few more functions***
**************************
**** Few more functions***

MeasureStop("1020_ RANK_PREFERENCE"); // Custom Timer - stop for
Rank Pref page
==========================================================

With the inclusion of Think Timer (wait time kept deliberately to simulate
real user behaviour as a typical user waits on a page before performing
any action) script would look as following -

===========================================================
MeasureStart("1020_ RANK_PREFERENCE"); // Custom Timer - Start for Rank
Pref page

WebUrl("https://test-qa.test.edu/testtesting/images/arrow.png");

ThinkTime(154.56); // Think timer inserted in middle of Measure Start and
Stop timers.

**** Few more functions***
**************************
**** Few more functions***

MeasureStop("1020_ RANK_PREFERENCE"); // Custom Timer - stop for Rank
Pref page
============================================================

Having think time in middle of Start and Stop timers would cause think time to
be added to the overall response time which eventually would give a false
impression about the response time of page.
To avoid think time from being added to custom timer one needs to stop timing
measurement before Think Time and must resume it after it. This is as following
-

==============================================================
MeasureStart("1020_ RANK_PREFERENCE"); // Custom Timer - Start for Rank Pref
page

WebUrl("https://test-qa.test.edu/testtesting/images/arrow.png");

MeasurePause("1020_ RANK_PREFERENCE"); // Pause the time measurement
ThinkTime(154.56); // Think Time
MeasureResume("1020_ RANK_PREFERENCE"); // Resume the time measurement

**** Few more functions***
**************************
**** Few more functions***

MeasureStop("1020_ RANK_PREFERENCE"); // Custom Timer - stop for Rank
Pref page
=============================================================

This how think time can be stooped from getting added to custom timers.

fwait-Parameter:
When browser-level Web traffic is recorded using the Recorder, a wait time is
included at the end of recorded functions to tell the replay engine how long to
wait before executing the next function in the script. In WebURL function it
look as -

==============================================================
WebUrl("http://www.shopit.com/ad.gif", 17.2); // Here 17.2 is fwait parameter.
==============================================================
The wait time times simulate:

* The time the browser needs to parse out links of embedded documents (e.g.
images, etc).
* A users thinking time.

This wait time is ignored in Stress Test mode.

But again this wait gets added to custom timers and results in overall high
response time. If WebUrl function is just a call to image then it can be
manually removed from the script, But if its need is indispensable then it can
be replaced with equivalent Think Timer as -

===========================================================
WebUrl("http://www.shopit.com/ad.gif"); // WebURL function with out fwait.
ThinkTime(17.2); // Think time to simulate the wait period
===========================================================

Here again time measurement should be stopped before Think Time and should be
resumed just after it as illustrated above.

Comments

Popular posts from this blog

Appium and android mobile app automation

Next appium and Android mobile app automation video tutoria l is live. If you are new to appium then please check - appium-tutorial This video tutorial covers - Start vysor (Just for this session and not mobile automation :)) Start appium and start appium inspector Desired Capabilities platformName - Android deviceName - L2N0219828001013 (as seen on "adb devices") Saved Capability Sets Start Session Scan app elements using appium inspector Get appPackage and appActivity using "APK info" app Install "APK info" app and open app whose appPackage and appActivity are required i.e. calculator Check top section of app icon com.android.calculator2 is app package com.android.calculator2.Calculator is app activity testng.xml file settings for running Android app tests Test details com.seleniumtests.tests.mobile.AndroidAppTest and CalculatorScreen class View beautiful STF test report  

Verify email confirmation using Selenium

Note: If you are new to java and selenium then start with selenium java training videos .     Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -