Convert LoadRunner
in to JMeter Scripts
We can also convert LoadRunner
scripts into JMeter scripts.
To do so, we divide
this activity into two parts
1.
JMeter
Side
2.
LoadRunner
Let s start with
JMeter Part:
As we know that JMeter
is based on a built-in proxy server that enables intercepting HTTP requests
that flow through it, and then converting them into HTTP Request samplers.
Steps to start:
1.
Go
to File -> Templates -> Recording
2.
Click
the “Create” button
Now, JMeter will
populate a Test Plan that is suitable for HTTP(S) traffic recording.
3.
Expand
“WorkBench -> HTTP(S) Test Script Recorder” and click the “Start” button.
4.
Once
we click the “Start” button
JMeter will show a message telling that a
certificate was created in JMeter’s “bin” directory.
5. Import the
certificate in trusted group under security.
Before clicking on “OK”,
Lets move to LoadRunner part:
converting a
LoadRunner test to JMeter is replaying a test in LoadRunner by using JMeter as
a proxy, so JMeter can capture the requests and convert them to its own Test
Plan format. Therefore, we need to “tell” LoadRunner to use JMeter as a proxy.
1. Open LoadRunner
VuGen
2. Open the script
you want to convert into JMeter format
3. Click “Replay
-> Settings”
4. In the “Runtime
Settings” locate “Internet Protocol -> Proxy” and amend the configuration as
follows:
- Proxy: Use Custom
Proxy
- Use the proxy
server
- HTTP Proxy: enter
the IP address or hostname of the machine, where JMeter is running. If VuGen
and JMeter are running on the same machine - type localhost there.
- Port: use 8888
(unless you changed the port in JMeter’s HTTP(S) Test Script Recorder
That’s it, now hit F5
(or click “Replay -> Run”) to kick off LoadRunner test execution.
Now, JMeter will
record all the HTTP requests and we will be able to observe them under JMeter’s
Recording Controller.
Note:
- Make sure that Do
not use a proxy server for local (Intranet) addresses is NOT CHECKED
Happy Testing!!!
Comments
Post a Comment