Ruth Kusterer is a technical writer for BlazeMeter

Become a JMeter and Continuous Testing Pro

Start Learning
Slack

Test Your Website Performance NOW! |

arrowPlease enter a URL with http(s)
Jul 01 2020

How to Run Scriptless Testing in BlazeMeter

 
 

BlazeMeter's new, equally user-friendly Scenario Editor for Scriptless Testing now makes it easy to keep your recorded GUI Functional Tests up-to-date and expand on them: You can simply move, drag, and drop predefined actions and objects into your test scenario. This building block approach to test creation is a great way to also let team members contribute who cannot (or do not want to) write scripts manually.

 

  • Every time you change the building blocks in the scenario editor, the script behind it is updated, and you can immediately run the test from the browser.
  • Every time you record a new test in your browser, new objects are added to the Test Object Library.

 

What exactly are these building blocks of a Scriptless GUI Functional Tests? You apply test actions to test objects, just as a tester would do when writing a script. By actions we mean familiar interactions such as clicking, typing text, or selecting. And buttons, form fields, and menu items are our test objects.

 

If you can describe your acceptance test as steps in an Agile Story, then you can create it in BlazeMeter.

 

Getting Started With Scriptless Test Automation with BlazeMeter

 

How does it work? You already know that you can record test cases using the BlazeMeter Recorder Chrome extension, available for free from the Chrome Store.

 

1. Log on to your BlazeMeter.com account.

2. Open the Recorder extension in Chrome. First, make sure that you are in the right project:

   a. Click the Project Name in the bottom right of the extension.

   b. Select your Account, Workspace, and Project.

   c. Click Save and Go Back.

3. Open the web application under test in Chrome.

4. Open the Recorder and click Start Recording.

 

Scriptless Test Automation from BlazeMeter

 

5. Perform the steps of the test case.

   a.For example, select menu items, click buttons, resize windows, interact with the app as usual.   

   b. Every few steps, right-click on the page and select BlazeMeter | The Continuous Testing Platform, assert... from the context menu to add assertions to your test.

 

Scriptless Testing Getting Started

 

6. When you have performed all steps of the test case, click Stop.

 

Test Automation Scriptless

 

The Extension saves the recording and closes.

 

7. Click the Recorder Extension again, and click Run..., GUI Functional (Selenium).

 

Scriptless Testing Getting Started

 

The test recording opens in BlazeMeter in the workspace and project that you assigned in the Chrome extension.

 

Scriptless Test Automation from BlazeMeter

 

What is the Scenario Editor?

 

You are likely already familiar with recording test scripts using the Recorder extension. Now, with the release of BlazeMeter Scriptless Testing, you additionally have access to a user-friendly visual Scenario Editor.

 

BlazeMeter converts the recording into test steps (such as opening a web page, typing text, clicking a button, selecting a menu item), and displays the steps as boxes in the Scenario Editor:

 

Testing without Scripting

 

  • Each step is automatically mapped to an action (click, type, select, assert, and so on).
  • Each object that you interacted with during the recording (a button, a menu, a text field, and so on) is automatically added to your Test Action Library.
  • If the object was already in the Library from a previous recording, BlazeMeter recognizes it and re-uses the existing object.

 

Scriptless Test Automation from BlazeMeter

 

Your populated Test Action Library (and your custom objects in it) is shared with your team members in the same workspace. This means after one team member records a new object, all the others can reuse it.

 

The Scriptless Testing scenario editor makes it easy for you and all your team members to contribute recorded test cases, to edit recorded test cases, or to create new test cases from scratch. In the following example screenshots, we have recorded ourselves selecting departure and destination cities on a flight booking web application.

 

How Can Scriptless Testing Help You To Test More, and Test Faster?

 

What can we do with this recorded test, without any scripting experience?

  • You can duplicate test scenarios, edit them, and run them as new test cases.
  • You can duplicate, move, or delete test steps within scenarios.

 

Test Automation Scriptless

 

  • You can change actions, objects, and values by simply selecting from a menu.

 

Scriptless Testing Getting Started

 

  • You can drag and drop actions from the action palette onto the canvas, and apply these actions to existing objects in your Library.

 

Test Automation Scriptless with BlazeMeter

 

  • The whole while in the background, BlazeMeter automatically turns your scenario into a valid test script in YAML format.

 

YAML script in BlazeMeter

 

With BlazeMeter Scriptless Test Automation, all your subject matter experts can finally contribute test cases -- no scripting experience required.

 

Scaling Up Scriptless Testing with Test Data

 

After you get the hang of Scriptless Test creation, you might want to scale it up. Instead of just considering one variant, you want to test different combinations of interactions that could also cause errors. You do not enter only names, but also various unicode characters and punctuation; or you need to test any selections from an ordering menu in combination with different delivery options.

 

You don't have to record each of these test recombinations manually! Instead, you replace the hard-coded target object with a variable keyword, and upload a spreadsheet that spells out all the value combinations. BlazeMeter will then automatically run tests with the variations you specified.

 

Scriptless Testing Improves Agile Testing For Your Whole Team

 

BlazeMeter knows how Agile Teams work and makes it easy to share test data and tests with the team. We recommend creating a workspace for every test suite that uses the same set of objects in the object library. When one team member updates a test or an object, they can choose to propagate this change to all others who re-use it. Team members can check the revision history and find out why an object was updated and by whom.

 

More Accurate Debugging

 

It's possible that a recorded test fails at a later point, for example, because a GUI element was renamed, or did not load fast enough. The Scenario Editor highlights the broken test step and helps you get to the bottom of the problem quickly. And in stubborn cases, a fellow tester can always troubleshoot and update the script using the built-in debugger.

 

Ready to get started? Log in to your BlazeMeter account, or fill in your URL in the box below to start testing.

   
arrowPlease enter a URL with http(s)

Interested in writing for our Blog?Send us a pitch!