Creating Scriptless Functional Tests

You can create and edit GUI Functional Tests manually by dropping pre-defined Actions and Objects into a Test Scenario. This scriptless test creation approach is the preferred method for testers who do not want to write and upload scripts manually. Every time you change the building blocks, the Taurus script behind the scenario editor is updated, and you can immediately run the test.

Record scriptless GUI Functional Tests using the BlazeMeter Recorder Extension. Advanced users can also choose to use the integrated Debugger to troubleshoot Scriptless tests.

To edit Scriptless GUI Functional Tests, you need to understand the following concepts: Objects (GUI elements such as buttons and fields), Actions (such as click or select) and Groups.

1. How to Create a Scriptless Test Manually
   
2. How to Create Objects
3. How to Edit Objects
4. How to Define Scenario Steps
5. How to Create Groups
6. How to Edit Groups

How to Create a Scriptless Test Manually

1. Ensure you have the "Functional" tab selected.
   
2. Click the "Create Test" button near the top-center of the screen.
   
3. Click the "GUI Functional Test" button to create a new test.
   
4. Under Configuration, Test Definition, click the Pencil button to give the test scenario a name.
5. Define your Scriptless test in one of the following ways:
   • Record Test Scenarios in Chrome
     1. Verify that you have the BlazeMeter Extension installed. For more information, see The BlazeMeter Chrome Extension.
     2. Click Start UI Recorder on an empty canvas.
        A new browser window opens. The Chrome extension opens.
     3. Open your web app and perform your test steps. For more information, see Chrome Extension - Record.
     4. When you're done, click Stop Recording in the Chrome Extension.
        The recorded test opens in the Scriptless Scenario Editor.
   • Build Test Scenarios out of building blocks
     1. Drag Actions from the Groups and Actions tabs and drop them onto the scenario canvas.
     2. For each Action, define step name, target object, and values:
        
6. Click the Debug Test button to do a test run. A test run does not count against the metrics.
7. Click the Run Test button to execute your test.
   

Scriptless Scenario Creation Tips

• Drag steps to reorder them in the scenario list.
• Click the trash can button to remove a step from the scenario.
• Click the Duplication button to create an editable copy of a step.
• Use the searchbars to quickly find Objects, Actions, and Groups by name.
• Click the Screenshot button to view what the Object looks like in the user interface.

Test Execution Settings

• Location:
  You can choose a specific public Cloud or private location to run the test. For more information, see Cloud vs Private Location and Get the Location Name.
• Browser:
  By default, the test runs in the latest Chrome browser. If you have created a private location that has other browsers and versions configured, you can select specific browsers in which to run the test. For more information, see Supported browsers.
• Mock Services Configuration:
  If you have created a mock services configuration, you can assign it to this test.

How to Create Objects

Objects are GUI elements in your system under test, such as text fields and buttons. When you start a new project, your Object list is empty. You manage Objects from the Test Action Library tab. To create an Object, you must provide a unique way to locate the element in the DOM.

There are several ways to create Objects:

• Let the BlazeMeter Chrome Extension record and create Objects automatically.
• Use the Object Picker to change an existing object.
  
• Create Objects manually, straight from the test definition window.
  
  

How to create Objects manually:

1. Add an Action to the scenario.
2. Select the Object comboBox and select Create New Object.
3. Define an Object Name.
4. Select one or more of the following Locator types:
   • By CSS Class
   • By ID
   • By Name
   • By Xpath
5. Define the locator Value as a text string, for example, identify the object by its ID.
6. Click Create.

The Object is added to the Object library for this project and can be used in this test.

How to Edit Objects

From the Test Action Library, you can only edit the name and description of Objects. Editing other Object properties impacts Scenarios in ways that require debugging and validation, which can only be done when the Object is used in the context of a scenario.

1. Find the Object inside a step in the Scenario Editor and click the step to select it.

   Tip: Use the Test Action Library to find where the Object is used if you cannot find it in a Scenario.

2. Click the Edit Object button (pencil icon) and modify locators manually, or click the Object Picker button (arrowhead in square icon) and then click an object in the web app under test.
   
3. (Optional) Uncollapse and review the revision history of the Object. The change log contains the time of the edit, who made the change, and a change note.
4. Make your changes and save.
5. Debug your test to verify results.
6. (Optional) Click Override Group Action to save your changes to the shared Test Action Library.

How to Define Scenario Steps

You create scenario steps out of Actions, Objects, and Parameter Values.

The Taurus Actions are a predefined set, you cannot create new Actions. Available Actions include assertions, clicking buttons, selecting dropdown items, entering text, pausing, submitting a form, opening URLs, and many more.

For each scenario step, you can define a name, an Action, an Object, and values. The following example shows a test step that selects a flight departure time of 10:00 o'clock from a menu object.

In a test step such as clicking a button, or typing text into a form field, an Action is applied to an Object. Use the Object menu to search the project for existing Objects or to record new Objects, such as buttons.

Lastly, define values, if applicable. A value can be, for example, a name to enter into a form field, a post code number, a time selected from a selector, a URL, and more. Not all actions require values.

Tip: Instead of hard-coding values, you can parameterize your test and define dynamic test data values. After you have defined Data Parameters, you can select them from Value dropdown as well.

How to Create Groups

A custom Group contains multiple Actions that occur together in a given order. For example, you can create a custom "Login" Group that contains a sequence of three Actions, "Enter User ID", "Enter Password", "Click Submit".

Groups are useful because they can be shared, but not a requirement to create scenarios. You add Groups to a scenario in the same way as you add single Actions.

To create a Group straight from the Test Definition, drag a sequence of Actions into the Scenario Editor, and select their check boxes. The selected steps must be consecutive without gaps. Then enter a name for the Group and click Save As Group Action.

It is possible to nest Groups inside other Groups, but you will not be able to drill down and edit nested Groups directly in the Scenario Editor.

How to Edit Groups

From the Test Action Library, you can only edit the name and description of Groups. You edit the Actions, Objects, and values inside a Groups from the Scenario Editor. Such local changes are automatically saved only in the current scenario.

You can choose to overwrite the values of the original Group in the Test Action Library, or choose to save your changes as new Group in the Test Action Library.

1. Find the Group in the Scenario Editor and expand it.
   

   Tip: Use the Test Action Library to find where the Group is used if you cannot find it in a Scenario.

2. Click the Edit button (pencil icon) to edit elements of the Group.
3. Debug your test to validate your changes.
4. (Optional) Click Override Group Action to save your changes to the shared Test Action Library.

Important: If you overwrite Groups, your changes affect other test scenarios (and other users) that embed shared resources from the Test Action Library. If you save your changes as a new Group, the new Group becomes available to other users through the Test Action Library without impacting existing tests.