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

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

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

Using xPath to reach parent of an element

Well, I am big fan of css locator my self there are times when css locators don't fit requirement. One such requirement is when you want to navigate to parent element of an element and may be parent of parent and even more. Unfortunately css locators don't provide any mechanism to navigate to parent of an element. See this for more. Of late I came across a scenario when I wanted to click on a link depending upon the text in a text box. Herein parent of text box and parent of link were at the same location. More over there could have been many such combinations in application. Fortunately I just need to pick first such instance and Web Driver any way considers only first instance when multiple locators are found matching an element. Element in question is in following html - Here I need to click on highlighted anchor on the basis of input element (which is also highlighted in image) Herein first I need to reach div parent (class = 'left couponmainarea