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

Verify email confirmation using Selenium

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

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

Return only first or last element from webelements collection

We often come across situation when there are multiple elements on a page and we probably like to exercise only a few of them using selenium webdriver. May be just first and last element. For example on a search result page we may like to click on only first and last link and not all. This is when Iterables API comes handy. (By the way I am assuming that you have already completed watching selenium training videos :)). Once we have collection of web element then we can use Iterables to get only first or last element as following - Consider that we fetch collection of element as - List< WebElement > webElements = getDriver().findElements(By. id ( "htmlID" ));   Now we can get the first web element from this collection as -  WebElement firstElement = Iterables. getFirst (webElements,  getDriver().findElement(By. id ( "defaultElement" )));   Herein second argument -   (getDriver().findElement(By. id ( "defaultElement" )))    in the me