Skip to main content

User Actions

The Autonomous Natural Language Processing (NLP) engine allows you to effortlessly create a custom flow test using simple, everyday language. This powerful technology lets you define steps using common English phrases like "Browse to http://example.com/" or "Click the OK button" without any coding required. You can include variables or parameters in a test to allow you to run the test in different scenarios.

As you enter instructions for a step, Autonomous provides helpful suggestions to guide you through the process.

Auto-Correction​

The system automatically corrects syntax errors and divides complex steps into multiple simple steps, making them easier to read and understand. The Auto-Correct feature makes the following corrections to commands:

  • Grammar and Spelling – For example, "Clack OK" will automatically be corrected to "Click OK".
  • Break Down Complex Steps – Steps with multiple actions will be broken down into shorter, more manageable steps. For example, "Enter 'John' in 'User name' and click OK" will be divided into:
  1. Enter 'John' in 'User name'
  2. Click 'OK'
  • Simplify and Standardize Commands – Steps will be modified to ensure consistency and clarity across all steps. For example, "In the user name field, enter 'John Smith'" will be changed to "Type 'John Smith' in the 'User Name'".

If steps were corrected, the icon indicates the number of corrections made. Hover over the icon to view details of the changes.

Examples​

Below are examples illustrating how easy it is to create tests using Natural Language Processing. Notice how the commands are written in straightforward English, making them accessible even to those without programming or technical expertise.

Fill Out a Form​

Go to https://sandbox.applitools.com/
Click "Form"
Type "Jane Smith" in the "Your Name" field
Enter "janesmith@example.com" in the "Email" field
select "Technical Assistance" from dropdown below "Contact Reason"
Press ENTER
Click "Submit"

Open E-Commerce Page and Add Item to Cart​

Go to https://sandbox.applitools.com/
Click "E-Commerce App"
Click "Outdoors"
Click "Small Succulent Planter Pot"
Select the second option from the "Variants" dropdown
Click "Increment"
Click "Add to cart"

Entering Instructions​

When entering an action, identify a screen element, such as a button, text box, or image, and then specify what to do with that element, such as click, hover, or enter text.

Elements​

Elements on the page can be identified in various ways, including:

  • Text label, for example, "Get Started" button.
  • Position in a list, for example, "The third item in the Language list".
  • CSS Selector or X-Path selector ID, for example, "gh-minicart-hover".
  • Position in relation to another item, for example, Checkbox to the right of "I agree".
  • Location on the page, for example button at the top of the page.

Screen elements with more than one word should be in quotation marks ("...").

Common Commands​

Here are examples of common commands that the NLP engine supports. This is not a complete list, as there is no limit to the types of commands you can create.

Masking Secret Test Data​

If a step includes sensitive information, such as a password, PIN number, credit card number, or a URL with basic authentication, when you save the test, the sensitive data is stored encrypted on the server and masked in the interface. If the field is not automatically masked based on the name of the field, enter "Secret" before the field value to indicate that it should be masked. Once a secret value has been masked, there is no way to retrieve the value from the system.

In the following examples, the bold text will be masked:

Type "My-PASS" in the password field

Type secret "My-PASS" in "Value1" field

Navigate to "https://Username:**My-PASS**@autonomous-demo.applitools.com/basicAuth"

XPath Elements​

When recording a test in the interactive browser, there may be rare situations where the recorder is unable to assign a clear English name to a screen element. In this case, the recorder will identify the element with its XPath, which may be a long string of code, such as /HTML[1]/BODY[1]/DIV[5]/DIV[1]/MAIN[1]/DIV[2]/DIV[3]/DIV[4]/FIELDSET[1]/DIV[1]/DIV[3]/LABEL[1].

This can make the test more difficult to read; however, the test will still run successfully, and regular functionality, such as self-healing, will be applied to the element.

If you need to refer to the element in other steps in the test, you should identify it with the XPath. For example:

Click the "OK button" with the XPath selector "/HTML[1]/BODY[1]/DIV[5]/DIV[1]/MAIN[1]/DIV[2]/DIV[3]/DIV[4]/FIELDSET[1]/DIV[1]/DIV[3]/LABEL[1]"

Advanced Options​

A custom flow test can also include the following advanced commands: