Generative AI-Based Testing Certification

Your Progress: out of 29

Entering Data

You need to specify the string which you want to enter into the field as well as the field where it should be entered:

enter "olive oil" into "search"

You can use relative locations to help locate elements that are harder to pinpoint. However, this should be reserved for when there are several instances of the desired element.

enter "olive oil" into "search" to the left of "Accounts and lists"

If the previous step has already put the cursor onto the input field, you can use type command without specifying the input field name:

click "search"
type "olive oil"

Also use ‘type’/’enter’ to simulate pressing a key or a combination of keys on the keyboard.

type enter 
type ctrl a

For multi-line text inputs, all you need to do is specify lines, as well as the end of the text:

enter text starting from next line and ending with [END]
Hello Max,
Let's discuss the opportunity
[END] into "Notes"

Using AI to enter values

testRigor can use AI to enter values into fields on the UI.

This is especially useful when you are unsure about an element’s name, placeholder, or any other unique identifier.

Example:

enter "kindle" into "search bar" using AI

Here, "search bar" is the prompt to AI, instructing it to locate the input field. AI understands from the command that the goal is to enter a value into a UI element.

AI is not applied to the entire command, it is specifically used to find and identify the target field (“search bar”) on the page, leveraging both the page source and the screenshot for better accuracy.

There are also variations of the enter command using AI.

Example:

generate from template "%*********************************", then enter into "search bar" using AI and save as "generatedDescription"

In this case, AI still focuses solely on finding the “search bar” on the page, while the rest of the command handles value generation and saving.

Checking checkboxes

There will typically be multiple checkboxes on the page. In this case, you need to provide additional context – so that testRigor knows which checkbox you want to use. You can use the browser’s inspect feature to locate the label of the element, or its id, or use a relative location.

click checkbox to the left of "Add to cart"

We can also click by indexes, which means using the 1st, 2nd, 3rd, etc instance of an element on the page.

click 2nd checkbox "id"

Some checkboxes use binary inputs (0 = off, 1 = on). Clicking with JavaScript doesn’t always toggle the checkbox.

In these cases, you can use the enter command to explicitly set the checkbox state instead.

enter "1" into "checkbox_3"
enter "on" into checkbox to the left of "Add to cart"

Explicitly setting the state can make test cases more predictable and reliable in certain situations.

Native dropdowns

Native browser dropdowns can be identified by the HTML <select> tag. For these dropdowns, use the select command and specify the value and the name of the dropdown:

select "Books" from "All"

You can also select by the number the option appears in the dropdown:

select 1st option from "MySelect"
select second option from "MySelect"
select option 10 from "MySelect"

Read full documentation about entering data here.

Custom dropdowns

Dropdowns generally fall into two categories: native browser dropdowns and custom dropdowns. Unlike native dropdowns, which require direct interaction with the browser, custom dropdowns are interacted with through UI actions such as clicking and typing.

Custom dropdowns are typically represented in the DOM as either <div> or <input>, allowing them to be interacted with using clicks, similar to how a user would.

The following are the two most common types of custom dropdowns:

Standard dropdown:

The best way to interact with this type of custom dropdown by clicking on the dropdown to expand it, and then clicking on the value.

click "Select Year" on the right of "Model"
click "2017"

Auto-suggest dropdown: A users clicks a dropdown and types a partial or full term after which the dropdown displays options limited to those that match the string typed and the user clicks on the desired option.

There are two ways to interact with this type of custom dropdown:

Enter and click (works better when the element is tagged as an <input>):

enter "react" into "React Dropdown Select"
click "ReactDropdownOption1"

Click, type, and click (works better with <div> tags):

click "React Dropdown Select"
type "reactdrop"
click "ReactDropdownOption1"

*Note that a partial string is preferred for the option typed into the field, and the full string is preferred for clicking. This is to avoid having two of the same exact strings on the page when the click command is used.

testRigor has 3 options to identify dropdowns, this setting can be changed under Settings > AI > Dropdown detection strategy. Typically you might want to change it only if detecting dropdowns takes too long, and you want the test to run faster.

Use Machine Learning to detect dropdowns – Default option, but it is also the slowest due to the fact that it uses machine learning
Optimistic, attempt to guess dropdowns – Turns off machine learning, but still uses other intelligence resources
Pessimistic, only rely on known dropdowns – Depends solely on the basic functionality, but it is the fastest. (<select> tags use the select "item" from "dropdownName" command; <div> and <input> tags are dealt with by clicking)

Generative AI-Based Testing Certification Your Progress: out of 29