Skip to main content

Recording curl request with JMeter Recorder

Though it is quite east to convert curl requests to corresponding JMeter request. At times you might be stuck with issue like I faced when uploading a file with JMeter HTTP request
In a gist I kept getting 404 error when using REStful service to upload a file. After days of investigations I found it that I should be using HTTP request implementation java and not HttpClient4. JMeter HTTPs Test Script recorder was of great help to debug this issue. This post describes the process of recording curl request through JMeter HTTPs Test Script recorder.

If you have never used JMeter HTTPs Test Script recorder then create a new JMeter Plan and under WorkBench > Add > Non Test Element > HTTP(s) Test Script Recorder. 
Specify Global Setting > Port as 8090

If we were using browser to record web application then we would configure its proxy to (Since http proxy server would work on localhost) and port 8090 -

Any way, we are not going to record browser actions but a curl request.

Under Test Plan element add Thread Group, Recording Controller and HTTP Request Default. Under HTTP Request Defaults mention Server IP as localhost” and port as 8090. This is to avoid duplication from HTTP Requests during recording. Recording Controller is where recorded samples would appear.

In the end Test Plan would looks as - 

To be able to record curl request on JMeter, we have to specify proxy server on curl using --proxy flag. The curl request looks as - 

curl -k --proxy -X POST --header 'Content-Type: multipart/form-data' --header 'Accept: application/json' --header 'Authorization: bearer xxx' -F upload_file=@"/Users/tbhadauria/Documents/test.pdf"  'https://xxx'

Notice that I also added flag "k" to turn off curl's verification of certificate. Now hit the "Start" button on HTTPs Test Script Recorder and execute curl command. Following this you would find recorded elements under Recording Controller as following - 

I had already setup curl request on JMeter and comparing it to recorded elements I found that the only difference was the HTTP Request Implementation. I was using HTTP Request Implementation HTTPClient4 which would result in 400 error while recorded element had HTTP Request Implementation Java and it worked successfully. 

And this solved the issue of 400 error when uploading document using JMeter :) 

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