Skip to main content

Regular Expression extractor and JMeter

When using JMeter for performance testing of RESTful services, you may come across situations when you have to extract response from one request and pass it on to another request. This can be accomplished using regular expression extractor. You may like to watch JMeter training video on regular expression extractor if you have not already :-)

This post illustrates an example of extracting parameter from json expression without using any JMeter plugin. The drawback of using plugin is that you would have to make it available on each JMeter installation where you want to run the test.

Let's consider following JSON expression - 


   "access_token":"18b8b379-b875-467a-9f22-37b60024c1b9",
   "uid":"test user",
   "grant_type":"password",
   "scope": 
      "uid",
      "cn"
   ],
   "realm":"employees",
   "cn":"",
   "token_type":"Bearer",
   "expires_in":3599
}

Let's assume that we want to fetch value of access_token from this expression.
Then following regular expression can be used - 

"access_token":"(.+?)"

Let's look at these special characters one by one -

1 opening and closing parenthesis () enclose the portion of matched string to be returned
2 . means match any character
3 + means one or more times
4 ? means stop when first match occurs

without ?, the .+ would continue beyond first quotation " until it finds last quotation " and indeed this is not what we want.

For this specific example it is more efficient to use following expression - 
"access_token":"([^"]+)"
Herein [^"] means match everything except "
And matcher stops as soon as it finds first quotation "

Did you know that you can also test regular expression from with in JMeter? Run your test with 1 user and open results in ViewResultsInTree listener. ViewResultsInTree listener has a drop down to show results in different views. Select RegExpTester, paste your regular expression and hit Test button :-)



You may also like to see JMeter guide on Regular expression

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

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