BlazeMeter’s Google Chrome Extension allows you to test your application without prior scripting knowledge, by recording user actions and HTTP requests to create a unique test artifact that runs both JMeter and Selenium tests. 

Recording with the Chrome extension is one way to create Objects for the Test Action Library when you Create Scriptless GUI Functional Tests.

• Record Mode
  • Advanced Options
• How to Record a Test
  • How multi tab recording for Selenium scripts works
• BlazeMeter Script Editor
• How to Download the Recording

Record Mode

This mode automatically records in parallel performance and functional tests by creating both JMeter and Selenium scripts that can be tested locally or directly on BlazeMeter

First, let’s review the basic options available when you first open the extension:

• ENTER THE NAME OF THE TEST - Type the desired name of your test in this required field.

• Start recording - Starts recording both HTTP(s) requests and Selenium actions for the test.
  
  
• Stop recording - Stops recording the test.
  
  
• Reset all options - Resets everything, discarding any recording and settings and reverting the menu to its default state when you first opened it. 

• Run - This button is hidden and is enabled after the recording has stopped. Choose how to upload and run the script on BlazeMeter:
  
  • Performance Test
  • API Functional Test
  • GUI Functional Test
  • End User Experience Monitoring
    
    
• Edit - This button is hidden and is enabled after the recording has stopped. Use the JMeter Editor or the Selenium Debugger to make small fixes before uploading the script.
  
  
• Save... - This button is hidden and is enabled after the recording has stopped. Choose as what type of script to download the recording:
  • Taurus YAML of JMeter & Selenium - for Load and UX combined
  • Selenium only - for UX only
  • JMX - for Load only
    
    
• Save in Project... - Before you run or save the recording, select the target BlazeMeter account, project, and workspace where you want to save the test. 

The above options are all you need to record a simple script. There are additional advanced options available when needed. 

Advanced Options

These Advanced Options are specific to HTTP(S) calls. Scroll down to view all options in this section.

• User Agent - Select your preferred User Agent, meaning, which device or browser your users are using. This selection adds a “User-Agent” header to the requests, and it allows you to emulate various situations, such as a user browsing via a mobile device.
   
• Filter Pattern - By default, requests are not filtered; however, by modifying the match pattern in this field you can change which requests your recording includes. For example, you likely do not wish to record your Gmail, Facebook, or even BlazeMeter traffic. Typically you use this option to restrict requests to only one domain. You’ll be presented with the option to select which domains to include and exclude before the test actually runs.
  Default: http://*/*, https://*/*
  Format: Refer to Google’s guide on creating match patterns. 

• Disable Browser Cache - Disables the browser’s cache during the recording. This option is important since cached objects are not recorded.
  
  
• Wipe Service Workers - Removes the service workers of the page every time you navigate to another page while recording.
  

• Record AJAX Requests - Enable this option if the site uses AJAX which needs to be included in the recording.
  
  
• Update Settings Before Running Test - Enable this option to change test settings before running. Through the BlazeMeter interface, you can control properties such as ramp-up time, test duration, load distribution between engines, and much more.
  
  
• Randomize recorded think times - Enable this option to use a uniform random timer to simulate the expected delayed response time of a real service or human user. 

• Requests to Record - Lets you control how BlazeMeter handles embedded objects on the page, such as images, CSS, and JavaScript files.

• • Only Top-Level Requests - If selected, the recorded script will not include requests for referenced objects. When the script is executed, it will parse the HTML file and send requests for all referenced objects.

• • Top Level Requests and the Following - This option offers a selection of objects that can be included. The recorded script will include requests for referenced objects. When executed, the script does not parse the HTML file and likewise does not send requests for referenced objects. Here is an example of the choices that appear once this option is selected:
    
• GUI Functional Test Options
  • Export ID Locators - If the identifiers in your user interface are static, enable this option. This is the default. Examples of identifiers are "ID a1234567" or "Xpath div[id=a1234567]".
    If identifiers in your user interface may be regenerated and are not uniquely reliable for use in test scripts, disable this option. Disabling this option excludes ID locators from the recording. 
    The option is applied as long as you toggle it before you export and run the script in BlazerMeter, meaning, you can still toggle it after recording.

Now that we’ve outlined all of the available options, let’s walk through creating a simple recording.

How To Record a Test

By default, every Test Step you perform is being recorded to a “Test Case”, and it will be a monolithic script with a sequence of actions. On the JMX level, this will simply create a thread group consisting of these actions. The recorder, in fact, treats each step as a single transaction controller, so if you prefer, you may rename the label, and add additional labels to group subsequent actions under their own transaction controllers.

1. Once installed, click the BlazeMeter icon in your Chrome browser’s toolbar:
   
   
2. Login to your BlazeMeter account if you haven’t already. Verify the plugin is logged in via the “Hi [username]” greeting in the upper right-hand corner.
   
3. Give your test a name.
4. (Optional) Expand and configure advanced options, or use the defaults.
5. Click the Start recording button.
   The UI will change to show your yet-to-be-performed first step.
   Note that on the right-hand side there is a UI column and a JMX column, both of which start counting at (0).
   
6. Perform the actions in your application that you wish to simulate in your test. For example, browse to a site, click on a selection, fill out a form, submit the form. 
   Note that as you do so, the UI count increases to reflect UI actions you performed on a user-level, and the JMX count increases to reflect how many items are created within the performance script to do the same.*
7. (Optional) Rename the “Test Case” by clicking the label. Or type in a name, then click Save to create a new label under which to group sets of subsequent actions.
   
   The example above will appear as follows in the resulting JMX:
   
8. Use the Pause recording button at any time you need to pause the recording.
   The button will change to Record so that clicking it a second time will unpause, resuming the recording.
9. While the recording is paused, you can right-click any element on your webpage to add assertions as test steps. When you add an assertion, the UI count increments by one.
   
   Tip: Only add assertions while the test is paused, else the recorder will include the clicks you have performed to open the context menu.
10. When finished, click the Stop recording button.
    
11. Download, edit, or run the test in the cloud.
    

* The UI count and JMX count will often not match. This is because what might take a human multiple mouse-clicks (go to URL, expand the menu, selection option, click submit button) may translate into fewer, simpler actions to the machine (a GET followed by a POST) or the opposite, where just one user-action can cause multiple requests.

How multi-tab recording for Selenium scripts works

When recording a Selenium scenario the BlazeMeter Chrome extension takes into account the following scenarios:

• When you open a new tab, the Chrome Extension adds an "openWindow" action to your script recording with the default new tab url of Chrome. The Chrome Extension remembers this tab and the focus of recording switches to this tab using the "selectWindow" command.
• When you switch to an existing tab, the "openWindow" action is recorded together with the current URL of that tab. The Chrome Extension remembers this tab and the focus of recording switches to this tab using the "selectWindow" action.
• When you close a tab, the "close" action is recorded, then the browser automatically switches to another existing tab. See point 2 for the behavior of switching to existing tabs.
• When you switch between tabs that have already been part of the recording. In this case, the Chrome Extension does not add another "openWindow" action because it recognizes the tab. Instead, only the "selectWindow" action is added to the recording.

BlazeMeter Script Editor

Instead of downloading the recording as-is, you may wish to further edit your script. You have the following options:

• Load Testing: Edit your script for JMeter
• Functional Test: Edit your script for Selenium

Load Testing: Edit your script for JMeter

Click this option and you’ll see a new tab open to display the JMeter script editor.

The topmost three buttons allow you to select in which format to export your script: A Taurus YAML file, Taurus JSON file, or a JMeter JMX file. 

The buttons in the red bar allow you to expand all fields, collapse all fields, undo a change, or redo a change, respectively.

To the left of each item is a button you can click and drag to move the item up or down in the script, and a button that opens a menu for customizing your script:

Lastly, the play button in the upper-right corner will allow you to run your edited script on BlazeMeter.

Functional Test: Edit your script for Selenium

Click this option to open the recording in the BlazeMeter Selenium Debugger, which allows you to edit the actions (to modify values and element targets), and to replay your recorded steps using a playback feature.

The first four buttons are your main controls for replaying your script.

These buttons include:

• Resume replay - Click this button to begin or resume a replay of your script. You can then watch the Debugger perform the recorded actions live in your browser.

• Pause replay - While the replay is running, click this button to pause it.

• Stop replay - Click this button to completely terminate the replay.

• Adjust the replaying speed - Click this button to open a drop-down menu of options which allow to slow down or speed up the playback, or set it back to normal speed.

As the test replays, it will keep track of the success and failure of each action in the right-hand column.

To edit your recorded script, click and drag the handle on the left of the action to reorder steps, or right-click the button to open a drop-down menu to duplicate or delete the action, or add/remove a breakpoint during the replay.

You can click the upper right-hand Add Command button at the top of each group of actions to add a new action. This will add a new row at the bottom of the group, in which you can manually enter a action, target, etc.

Once you begin typing over “Command name” with an actual action, a pop-up menu will appear showing possible actions to use.

You can edit existing actions by clicking the down arrow to the right of each action, which opens a drop-down menu with various options. This arrow will only appear for certain types of actions, depending on whether these variables or parameters can be modified.

When you are finished editing your script, the buttons in the upper right-hand corner provide options for exporting it**.

These buttons include: 

• Load JSON file - Loads an existing JSON file from disk into the Debugger.

• Export to a JSON file - Exports your edited script to a JSON file.

• Export to .yaml - Exports your edited script to a Taurus YAML file. 

How To Download the Recording

Now that your script is recorded, you may immediately download the recording.

You will be prompted to select the desired type of the exported recording.

• A Taurus YAML script containing both, JMeter and Selenium tests.
• A Taurus YAML script consisting of only a Selenium test.
• A JMeter-only JMX script.

If you selected additional options for Requests to Record earlier, you will be prompted to select additional options pertaining to which domains to include in the exported script.