Skip to content
  • ZipCode Api
  • Blog
  • About RedLine13
RedLine13
RedLine13
Primary Navigation Menu
Menu
  • Start Testing
  • Demo
  • Pricing
  • JMeter
  • Partners
  • Docs
    • Documentation Home
    • AWS Set Up for load testing
    • AWS Approval for Large Tests
    • PHP, NodeJS, Python Load Tests
    • Scalability
    • Jenkins Plugin Setup
    • Premium Features
    • Knowledge Base

Recording with JMeter Proxy

By: RedLine13

A quick guide for getting started with JMeter Recording

1 – Start your JMeter Recording with the Recorder Template

Open JMeter and Select Templates from File menu

Screen Shot 2016-01-12 at 11.03.33 AM

Select the Recording Template and press ‘Create.’

Screen Shot 2016-01-12 at 11.10.37 AM

You now have a test plan with some basics already configured

Screen Shot 2016-01-12 at 11.04.57 AM

Why use the template?

The recording template will put in place a few items that are staples in JMeter tests.

  • User Defined Variables are created empty, however, in many tests you are going to want to pass in custom variables.
    • http://jmeter.apache.org/usermanual/component_reference.html#User_Defined_Variables
  • HTP Request Defaults is a configuration element that can control the defaults for HTTP requests to follow.  When you have a load test simulating many requests, this can simplify changes you want to make.
    • http://jmeter.apache.org/usermanual/component_reference.html#HTTP_Request_Defaults
  • HTTP Cookie Manager is the important inclusion for the template.  Without the cookie manager, most recordings will fail during playback as cookies will not be managed between requests.  The cookie manager has three purposes
    • Enable creating and setting user-defined cookies
    • Store and Send Cookies for requests
    • Define cookie behavior
      • Clear Cookies Each Iteration – every iteration it will wipe the stored cookies
      • Cookie Policy and Implementation – this has real consequences on how cookies are managed and sent via your web requests
        • We primarily stick to defaults to simulate a browser as close as possible.
      • Apache Docs – http://jmeter.apache.org/usermanual/component_reference.html#HTTP_Cookie_Manager
  • Workbench HTTP(s) Script Recorder
    • This element sets up some easy defaults for recording your web traffic.  The template configuration is different than just adding the recorder yourself.
      1. Port 8888 will be your proxy port.
      2. It will use Transaction Controllers to group requests.
        • Screen Shot 2016-01-12 at 11.32.12 AM

2.  Setup your browser to point to the proxy

This is also possible on a mobile device and works wonders, however this blog post is about desktop browser.

In many cases, you can use your system settings to control the proxy server, for example on OSX

Screen Shot 2016-01-12 at 11.36.30 AM

However, you can use browser specific configuration if you want to limit the proxy to a browser.  I typically use browser specific setup for my proxy.

Firefox

Firefox configuration allows changing proxy

 Screen Shot 2016-01-12 at 11.38.39 AM

Chrome

Chrome requires using an extension if you want to control in browser – proxy-switchysharp extension

 Screen Shot 2016-01-12 at 11.42.17 AM

Step 3.  Start your proxy and browse

After you press start, you will notice a generated certificate with instructions on how to install.  This step is critical if you are going to be browsing HTTPs sites as it will need to proxy your certs.

Screen Shot 2016-01-12 at 11.47.08 AM

You check if it works since the template adds a View Results Tree next to the recorder.

Screen Shot 2016-01-12 at 11.47.16 AM

Then you can browse into the Recording Controller node and see the test plan while it is actively created.

Screen Shot 2016-01-12 at 11.47.33 AM

Press Stop and that’s your JMeter Recording.

You now have a JMeter test plan you can reuse and tweak.

And you can use that for load testing. Read more.

2016-01-12
Previous Post: Writing Firefox Plugin to listen to HTTP Traffic
Next Post: What are my options for using Assertions in JMeter

Recent Posts

  • Guest Post – IoT Load Testing
  • Load Testing Users in India
  • Load Testing in India
  • Troubleshooting Common Issues with Selenium Tests on RedLine13
  • Extracting Metadata from Load Generator Instances

Related

  • Load Testing Users in India
  • Guest Post – IoT Load Testing
  • Guest Post: Load Testing with Locust and JMeter on RedLine13
  • Run Your RedLine13 Load Tests from Hyderabad, Jakarta and Melbourne
  • Load Testing in India
  • Selenium Basics for Load Testing
  • Pitfalls of Selenium Load Testing
  • Troubleshooting Common Issues with Selenium Tests on RedLine13
  • Extracting Metadata from Load Generator Instances
  • Case Study: iCIMS, The Talent Acquisition Software Experts

© RedLine13, LLC | Privacy Policy | Contract
Contact Us: info@redline13.com

Designed using Responsive Brix. Powered by WordPress.