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

Where is my defect ID?

Don't you feel ecstatic when your automated tests find bug? After all tests finding bugs give us a sense of accomplishment, is not it? And this is followed by usual cycle of defect reporting, retesting and hopefully closure of defect. But at times defects are deferred to next or future releases. Which causes test method to fail for subsequent releases. And if you are dealing with a test suite having 100s of tests then it may become difficult to remember if there was a defect reported for a failing test? How do you deal with such situation. How about adding defect-id to @description tag of TestNG test. Hence it is reported on automated test report and we would know if defect exists for a failing test - How do you track defect-id of a failing test?

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

Selenium Tutorial: Pattern Mathing using Selenium

I must confess I have never been admirer of Regular Expression but then there are times you can not escape from it, especially while working on a website which has dynamic contents appeared in static text and you want to validate it. like - "Validate that this text appears and there is 123 here and 456 here" And the test condition is 123 and 456 could be any three digits but number if digits should not be more than three. In a crude way we can at least test this - Assert.assertTrue(selenium.getText("elementLocator").contains("Validate that this text appears and there is")); but what if text goes wrong after "and there is"... what if more than 3 digits appear in text. This is where pattern matching/regular expression comes for our rescue and we can use matches method of String class to achieve same. So the assertion would be - String text = selenium.getText("elementLocator"); Assert.assertTrue(text.matches("Validate