Web Commands

🖥️ Web Commands

Testlum provides a wide range of commands specifically designed for web application testing.
Using these commands, you can interact with web elements, perform browser actions, validate page states, handle user inputs, and much more.

This section will guide you through the available web commands, their usage patterns, and best practices to build stable and efficient web tests across multiple browsers and devices.

📚 Categories

📚 Categories of Web Commands

Testlum web commands are grouped into the following functional areas:

🔹 Interaction commands

click

doubleClick

input

dropDown

hovers

hotKey

clear

dragAndDrop

🔹 Navigation and Scrolling

navigate

scroll

scrollTo

tab

switchToFrame

🔹 Assertions and Validation

assert

image

🔹 Utilities and Enhancements

javascript

wait

repeat

include

✅ Each category contains commands tailored to specific test actions, helping you quickly find and apply the right tool during scenario creation.

🌐 Base Command for Web Interaction

The <web> tag serves as the main interpreter for interacting with the user interface. It encompasses a set of commands, including navigation, waiting, and actions like clicking. The <web> tag organizes these commands into a single structure, allowing you to control browser behavior.

📋 Example Usage
<web comment="Start web scripts">
  
    <navigate command="to" comment="Go to base page" path="/shop/"/>

    <wait comment="Wait for visualizing a click" time="2" unit="seconds"/>

    <click comment="Click on the 'Shopizer' website link which opens in a new window" 
              locator="shopizer.webSiteShopizer"/>
  
</web>
✅ Tip:
The <web> tag allows you to bundle multiple actions into a single sequence for easy navigation and interaction with a webpage.

Interaction Commands

This section describes commands that simulate user interactions, such as clicking, typing, hovering, and dragging elements.

click

🖱️ `click`

The click command is used to simulate a user click action on a specific element on the page.

⚙️ Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the purpose of the click action
`locator`	String	✅	-	Locator ID or strategy to find the element to click
`method`	`selenium` `javascript`	❌	`selenium`	The click method to use (`selenium` or `javascript`)
`highlight`	Boolean	❌	`false`	Whether to visually highlight the clicked element (grey background, yellow border)
`condition`	Boolean	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded
`locatorStrategy`	String	❌	`locatorId`	Custom locator strategy if needed (more info in Locators Guide)

🧪 Example Usage

<click comment="Click on 'Sign In' button"
       locator="login.signIn"/>

✅ Tip:

Use highlight="true" during debugging sessions to see where clicks are happening!

Use method="javascript" if the Selenium click doesn't work (e.g., for hidden or tricky elements).

doubleClick

🖱️ `doubleClick`

The doubleClick command simulates a double-click action on a specified element.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the purpose of the double-click action
`locator`	String	✅	-	Locator ID or strategy to find the element to double-click
`highlight`	Boolean	❌	`false`	Whether to visually highlight the double-clicked element (grey background, yellow border)
`condition`	Boolean	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded
`locatorStrategy`	String	❌	`locatorId`	Custom locator strategy if needed (more info in Locators Guide)

🧪 Example Usage

<doubleClick comment="Double click on button" locator="login.button"/>

✅ Tip:

Use highlight="true" during debug runs to see which element is being double-clicked.

If the element is tricky to access (e.g., hidden under layers), consider using a custom locatorStrategy.

input

📝 `input`

The input command is used to enter text or file data into a specific field based on a locator.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the input action
`locator`	String	✅	-	Locator ID or strategy for the field to input into
`value`	String	✅	-	Value to be entered into the field (text or file reference)
`highlight`	Boolean	❌	`false`	Highlight the field during execution (useful for debugging)
`condition`	Boolean	❌	-	Condition to determine if this step should be executed
`locatorStrategy`	String	❌	`locatorId`	Custom locator strategy if needed (more info in Locators Guide)
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded

🧪 Example: Text Input

<input comment="Input first name"
       locator="ownerRegistration.firstName"
       value="Mario"/>
locator defines the UI element to interact with.

value is the text you want to input.

🖼️ Example: File Upload

You can also upload an image or file using the input command.
The file must be located in the same folder as your test scenario.

<input comment="Add profile photo"
       locator="userPhoto.addProfilePhotoButton"
       value="file:Firmino.jpg"/>
Prefix the value with file: to indicate a file upload.

Firmino.jpg should be placed in the same scenario folder.

✅ Tip:
Use highlight="true" when debugging forms or uploads to visually confirm the fields being targeted.

dropDown

🧩 `dropDown`

The dropDown command is used to select or deselect options inside a dropdown menu.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the dropdown interaction
`locator`	String	✅	-	Locator ID or strategy for the dropdown element
`type` (inside `oneValue`/`allValues`)	String	✅	-	Action to perform: `select` or `deselect`
`by` (only for `oneValue`)	String	✅ (if `oneValue`)	-	How to select an option: by `Text`, `Value`, or `Index`
`value` (only for `oneValue`)	String	✅ (if `oneValue`)	-	Value for selection according to the `by` strategy
`condition`	Boolean	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded
`locatorStrategy`	String	❌	`locatorId`	Custom locator strategy if needed (more info in Locators Guide)

🧪 Example:

<dropDown comment="Deselect all countries" locator="registration.country">
    <allValues type="deselect"/>
</dropDown>
<dropDown comment="Select first value from dropDown" locator="registration.country">
    <oneValue type="select" by="index" value="1"/>
</dropDown>

✅ Tips:

Use oneValue if you need to select/deselect a specific option based on its text, value, or index.

Use allValues only when you want to deselect everything from a multi-select dropdown.

hover

🖱️ `hover`

The hover command moves the mouse cursor over a specific UI element, triggering hover-based UI behaviors like dropdown menus or tooltips.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the hover action
`locator`	String	✅	-	Locator ID or strategy for the element to hover over
`condition`	Boolean Expression	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded
`locatorStrategy`	String	❌	`locatorId`	Custom locator strategy if needed (more info in Locators Guide)

🧪 Example Usage

<hover comment="Open drop down 'Novels' tab" locator="locator.novels"/>

✅ Tip:
Hovering can be used to reveal hidden menus or additional options without clicking.

hotkey

⌨️ `hotKey`

The hotKey command simulates pressing individual keys or key combinations on the keyboard, such as backSpace, copy, cut, enter, escape, highlight, paste, space, tab.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the hotkey action
`locator`	String	❌	-	Locator ID or strategy for the element associated with the hotkey action
`times`	Integer	❌	`1`	Number of times to repeat the hotkey action

🧪 Example Usage: Hotkeys with Locators

<hotKey comment="Paste the password">
    <paste comment="Paste the password"
           locator="hotKey.password"/>
</hotKey>

This example uses locator to specify the field where the hotkey (paste) will be executed.

🧪 Example Usage: Hotkeys without Locators

<hotKey comment="Click enter">
    <enter comment="Click enter" times="2"/>
</hotKey>

This example uses times to specify how many times the Enter key will be pressed.

✅ Tip:
For non-locator actions like tab, space, or backspace, just use the key name and set the times parameter to control how many times the key is pressed.

clear

🧹 `clear`

The clear command is used to clear any text or value entered in a specified input field.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the clearing action
`locator`	String	✅	-	Locator ID or strategy for the input field to clear
`highlight`	Boolean	❌	`false`	Whether to highlight the cleared field (grey background, yellow border)
`condition`	Boolean	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded
`locatorStrategy`	String	❌	`locatorId`	Custom locator strategy if needed (more info in Locators Guide)

🧪 Example Usage

<clear comment="Clear password"
       locator="demoNative.clear"
       highlight="true"/>

✅ Tip:
Use highlight="true" for better debugging during development to visually confirm that the field was cleared.

dragAndDrop

🏋️‍♀️ `dragAndDrop`

The dragAndDrop command allows you to drag an element from one location and drop it onto another.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the drag-and-drop action
`toLocator`	String	✅	-	Locator ID of the target location where the element is dropped
`fromLocator`	String	✅	-	Locator ID of the element to drag
`fileName`	String	❌	-	File name to upload during drag-and-drop (must be in the same folder as the test scenario)
`condition`	Boolean	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded
`locatorStrategy`	String	❌	`locatorId`	Custom locator strategy if needed (more info in Locators Guide)

🧪 Example Usage: Basic Drag and Drop

<dragAndDrop comment="Drag and drop action"
             toLocator="nativeDrag.dragFirst">
    <fromLocator>nativeDrag.dropSecond</fromLocator>
</dragAndDrop>

🖼️ Example Usage: File Upload with Drag and Drop

<dragAndDrop comment="Add image with dragAndDrop example" toLocator="dragAndDrop.image">
    <fileName>/home/user/image.jpg</fileName>
</dragAndDrop>

Use fileName to upload a file during the drag-and-drop action. The file must be located in the same folder as the test scenario.

🌍 Navigation and Scrolling Commands

Navigation and Scrolling Commands

This section covers commands that help you navigate between pages, scroll through content, and interact with frames.

navigate

🔄 `navigate`

The navigate command is used to perform different navigation actions, such as moving forward, backward, or reloading the page.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the navigation action
`command`	String	✅	-	Navigation action: `back`, `reload`, or `to`
`path`	String	❌	-	Path to navigate to when `command="to"`
`condition`	Boolean Expression	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded

🧪 Example Usage

<navigate comment="Go to register account page"
          command="to"
          path="/registerAccount"/>

Use command="to" with the path parameter to navigate to a specific URL or page path.

✅ Tip:

Use command="back" to go back to the previous page, or command="reload" to refresh the current page.

Great for testing flows like form submissions and multistep registration.

scroll

⬇️ `scroll`

The scroll command simulates scrolling actions either on the whole page or within a specific element.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the scroll action
`type`	String	✅	-	Type of scrolling: `page` for whole page or `inner` for a specific element
`value`	String	✅	-	Value of the scroll (e.g., number of pixels or percentage)
`direction`	String	❌	`down`	Direction to scroll: `up` or `down`
`measure`	String	❌	`pixels`	How `value` is measured: `pixels` or `percent`
`locator`	String	❌	-	Locator for the element if `type="inner"`
`condition`	Boolean	❌	-	Condition to decide if this step should be executed
`locatorStrategy`	String	❌	`locatorId`	Custom locator strategy if needed (more info in Locators Guide)
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded

🧪 Example Usage

<scroll comment="Scroll Down to 90 percent"
        value="90"
        direction="down"
        measure="percent"
        type="page"/>

value="90" means scroll to 90% of the page height.
measure="percent" sets how the value is measured.

✅ Tip:
Use type="inner" if you want to scroll within a specific element on the page (e.g., a long list or table). type="page" scrolls the entire page.

scrollTo

⬇️ `scrollTo`

The scrollTo command allows you to scroll directly to a specific element on the page.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the scroll-to action
`locator`	String	✅	-	Locator ID or strategy for the element to scroll to
`condition`	Boolean	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded.
`locatorStrategy`	String	❌	`locatorId`	Custom locator strategy if needed (more info in Locators Guide)

🧪 Example Usage

<scrollTo comment="Scroll to element" 
          locator="footer.registerButton"/>

locator specifies the element you want to scroll to.

✅ Tip:
The scrollTo command is helpful for bringing an element into view, especially when it's off-screen or hidden within a long page or container.

tab

🗂️ `tab`

The tab command allows you to perform operations with browser tabs, such as switching, closing, or opening new tabs.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the tab action
`index`	Integer	✅ (for `close` or `switch`)	-	Index of the tab to close or switch to. Default is the current tab if not specified
`url`	String	✅ (for `open`)	-	URL to open in a new tab.
`condition`	Boolean	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded

🧪 Example Usage

Switch to a Specific Tab

<tab comment="Switch to second tab">
   <switch index="2"/>
</tab>

Close a Specific Tab

<tab comment="Close tab with index 2">
   <close index="2"/>
</tab>

Open a New Tab with a URL

<tab comment="Open a tab via url">
   <open url="http://URL"/>
</tab>

Close the Current Tab

<tab comment="Close current tab">
   <close/>
</tab>

✅ Tip:

When closing tabs, if index is not specified, the current tab will be closed by default.

Use switch to easily switch between open tabs based on their index.

switchToFrame

🖼️ `switchToFrame`

The switchToFrame command allows you to switch the context to an iframe, either by locator or index.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the action to switch frames
`locator`	String	❌	-	Locator ID or strategy for the iframe to switch to
`index`	Integer	❌	`0`	Index of the iframe to switch to (default is 0)
`condition`	Boolean	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded

🧪 Example Usage

Switch to Frame by Locator:

<switchToFrame comment="Open API frame on the site"
               locator="frame.page">
    <input comment="Add email to the page"
           locator="frame.email"
           value="test@gmail.com"/>
</switchToFrame>

Switch to Frame by Index:

<switchToFrame comment="Switch to Frame by Index" index="1">
    <input comment="Add email to the page"
           locator="frame.email"
           value="test@gmail.com"/>
</switchToFrame>

Use index to switch to a frame by its index number (default is 0).

✅ Tip:
When working with multiple iframes, using index is useful if you don’t have a unique locator for the frame. Be mindful of the frame order, starting from index 0.

✅ Assertions and Validation Commands

Assertions and Validation Commands

This section describes commands that help you validate whether elements are present, data is correct, or actions succeed on the page.

assert

✅ `assert`

The assert command is used to verify conditions on the page, such as checking if elements are displayed or if data matches the expected value.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the assertion action
`condition`	Boolean Expression	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded
`locatorStrategy`	String	❌	`locatorId`	Custom locator strategy if needed (more info in Locators Guide)
`negative`	Boolean	❌	`false`	If `true`, asserts that the expected and actual content do not match

🧪 Example Usage: Assert by Attribute

<assert comment="Check that element is present on the page">
    <attribute comment="Assert 'password' field"
               name="class"
               locator="registration.inputPassword">
        <content>password</content>
    </attribute>
</assert>

💡 Tips on common attribute names:

innerHTML: Captures the HTML content inside an element (e.g., button text).

value: Often used for input fields (e.g., <input value="Test">).

href: For anchor links (e.g., <a href="/home">Home</a>).

src: For image or script sources.

data-*: Custom attributes like data-id, data-name — helpful for dynamic data.

class: Can be used to check if a specific style or state (like active, error) is applied.

✅ Use attributes to dynamically extract values for assertions, reuse in other steps, or debugging unexpected behavior.

🧪 Example Usage: Assert Multiple Elements

<assert comment="Test for Assert with sub-commands - notEqual, equal, attribute, title">
    <attribute comment="Assert 'password' field" name="name" locator="registration.inputPassword">
        <content>password</content>
    </attribute>

    <title comment="Check whether title of the page is correct">
        <content>Default store | Login</content>
    </title>

    <notEqual comment="Assert for check that 3 different contents are not equal">
        <content>one</content>
        <content>1</content>
        <content>{{ONE}}</content>
    </notEqual>

    <equal comment="Assert for check that two contents are equal">
        <content>one</content>
        <content>{{one}}</content>
    </equal>

    <present comment="Check that element is present on page" locator="forms.save"/>
    <present comment="Check that element is NOT present on page" 
              locator=".//img[@alt='Sunset in the mountains']" locatorStrategy="xpath" negative="true"/>
    <checked comment="Check that checkbox is NOT chosen" locator="uiElements.checkbox" negative="true"/>
    <checked comment="Check that checkbox is chosen" locator="uiElements.checkbox" negative="false"/>
    <alert comment="Check that alert text is equal to expected content">
        <text>Alert!</text>
    </alert>
    <alert comment="Check that alert text is NOT equal to expected content" negative="true">
        <text>Alert</text>
    </alert>
</assert>

✅ Tip:
Use negative="true" when you expect an element not to match the given condition, such as an element not being present, or an alert message differing from the expected one.

image

📸 `image`

The image command captures a screenshot and compares it to an expected image, validating visual correctness across the page or specific elements.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the image comparison action
`file`	String	✅	-	Path to the expected image file to compare against
`highlightDifference`	Boolean	❌	`false`	Whether to highlight the differences in the comparison (red for mismatched, orange for excluded)
`condition`	Boolean Expression	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded
`locatorStrategy`	String	❌	`locatorId`	Custom locator strategy if needed (more info in Locators Guide)

🧪 Types of Image Comparisons

fullScreen: Compares the entire screenshot.
picture: Compares an image element by its locator.
part: Compares a specific part of the page or element.

🧪 Example Usage: Full Screen Comparison

<image comment="Compare full screen with percentage less than 100" file="compare1.png">
    <fullScreen percentage="88"/>
</image>

percentage="88" specifies the accuracy for comparing the full screenshot.

🧪 Example Usage: Compare with Highlighting Differences

<image comment="Compare full screen" file="compare2.png" highlightDifference="true">
    <fullScreen/>
</image>

This will highlight differences in red and the excluded zone in orange.

🧪 Example Usage: Compare with Exclude Area

<image comment="Compare full screen with exclude" file="compare3.png">
    <fullScreen>
        <exclude locator="forms.username"/>
    </fullScreen>
</image>

The exclude parameter skips comparing the element specified by the locator.

🧪 Example Usage: Compare Part of Screen

<image comment="Compare a part of screen with percentage less than 100" file="compare4.png">
    <part locator="forms.form" percentage="99"/>
</image>

percentage="99" allows for a near-perfect match when comparing only part of the screen.

🧪 Example Usage: Compare an Image from the Page

<image comment="Compare image from the page" file="compare2.png">
    <picture locator="image.compare" attribute="src"/>
</image>

This command downloads the image from the page using the src attribute of the element found by locator="image.compare", and then compares it pixel-by-pixel with the local image file compare2.png.
The attribute="src" is used to extract the image URL from the page.

✅ Tip:

Image comparison works best with specific elements and smaller portions of the page (use part instead of fullScreen for better accuracy).

Ensure consistent screen dimensions when comparing full-page screenshots, as different device sizes can cause mismatches.

⚙️ Utilities and Enhancements Commands

Utilities and Enhancements

This section describes commands that provide additional functionalities, such as running custom JavaScript, waiting for elements, and repeating actions.

javascript

💻 `javascript`

The javascript command allows you to execute custom JavaScript code within the test scenario.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the JavaScript execution
`file`	String	✅	-	Path to the file in `data` containing JavaScript commands to execute
`condition`	Boolean	❌	-	Condition to decide if this step should be executed.
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded

🧪 Example Usage

<javascript comment="Your comment"
            file="function.js"/>

The file parameter points to a .js file somewhere in data folder with the JavaScript code to execute.

✅ Tip:

This command is useful for running custom scripts during your tests (e.g., changing a page's state, interacting with a JS library, or performing calculations).

wait

⏳ `wait`

The wait command pauses the execution of the scenario for a specified time, allowing certain actions or elements to load before continuing.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the wait action
`time`	Integer	✅	-	The time to wait, in either seconds or milliseconds
`clickable`	String	❌	-	Wait until a specific element is clickable
`locator`	String	❌	-	Locator of the element to wait for
`visible`	String	❌	-	Wait until a specific element becomes visible
`unit`	String	❌	`seconds`	Time unit for `time`: `seconds` or `milliseconds`
`condition`	Boolean	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded

🧪 Example Usage

Wait for an Element to Become Clickable

<wait comment="Wait for 10 seconds or less until element becomes clickable" time="10" threshold="1000">
    <clickable comment="Wait for 10 or less seconds until element becomes clickable" locator="login.signIn"/>
</wait>

Wait for a Specific Time

<wait comment="Wait 1 second" time="1000" unit="millis"/>

Wait for an Element to Become Visible

<wait comment="Wait 10 seconds" time="10000" unit="millis" threshold="500">
    <visible comment="Wait for 10 or less seconds until element becomes visible" locator="login.mail"/>
</wait>

✅ Tip:
Use threshold to limit the execution time, ensuring the test fails if the element is not found or the action does not complete within the allowed time.

⚠️ Note: The wait command is not the same as the global autowait setting in your configuration file. While autowait defines the default timeout for all element lookups, the wait command gives you explicit control over pauses and wait conditions inside the test scenario.

repeat

🔄 `repeat`

The repeat command allows you to repeat any action or sequence of commands multiple times. It is useful for actions that need to be executed a specific number of times or for running actions with different variations.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the repeat action
`times`	Integer	❌	-	The number of times to repeat the action (not used with variations)
`variations`	String	❌	-	Path to the variations file to run different data (not used with `times`)
`condition`	Boolean	❌	-	Condition to decide if this step should be executed
`threshold`	Integer (ms)	❌	-	Maximum allowed execution time; step fails if exceeded

🧪 Example Usage: Repeat Actions with Variations

<web comment="Start web scripts">
    <repeat comment="Check the ability to run variations in repeat" variations="variations_2.csv">
        <click comment="Click on registration button" locator="uiElements.register"/>
        <input comment="Input user email" locator="uiElements.email" value="{{variableFromVariationFile}}"/>
        <wait comment="Wait for 1 second" time="1"/>
    </repeat>
</web>

The variations parameter allows you to specify a file (like a CSV) that contains data for running the same actions with different inputs.

🧪 Example Usage: Repeat a Set Number of Times

<repeat comment="Repeat click and wait actions 5 times" times="5">
    <click comment="Click on drop-down" locator="uiElements.dropDownField"/>
    <wait comment="Wait for 2 seconds" time="2"/>
</repeat>

The times parameter sets how many times the actions inside <repeat> should be executed.

✅ Tip:

Use variations to automate testing with different data sets.
Use times to repeat actions multiple times (e.g., for load testing or reliability checks).

include

➕ `include`

The include command allows you to run one scenario inside another, making it easy to bundle multiple scenarios together for reusable actions or tests.

📋 Parameters

Parameter	Type	Required	Default	Description
`comment`	String	✅	-	Description of the included scenario
`scenario`	String	✅	-	Path to the scenario you want to include

🧪 Example Usage

<include comment="Add scenario for login to the system"
         scenario="/nameOfScenarioFolderWithSlash"/>

The scenario parameter specifies the path to the scenario from the scenarios folder that you want to include.

✅ Tip:
Use the include command to create modular and reusable tests. This allows for easy maintenance of larger test suites by grouping common functionality into separate scenarios.

Web Commands

🖥️ Web Commands

📚 Categories of Web Commands

🔹 Interaction commands

🔹 Navigation and Scrolling

🔹 Assertions and Validation

🔹 Utilities and Enhancements

🌐 Base Command for Web Interaction

📋 Example Usage

Interaction Commands

🖱️ click

⚙️ Parameters

🧪 Example Usage

🖱️ doubleClick

📋 Parameters

🧪 Example Usage

📝 input

📋 Parameters

🧪 Example: Text Input

🖼️ Example: File Upload

🧩 dropDown

📋 Parameters

🧪 Example:

🖱️ hover

📋 Parameters

🧪 Example Usage

⌨️ hotKey

📋 Parameters

🧪 Example Usage: Hotkeys with Locators

🧪 Example Usage: Hotkeys without Locators

🧹 clear

📋 Parameters

🧪 Example Usage

🏋️‍♀️ dragAndDrop

📋 Parameters

🧪 Example Usage: Basic Drag and Drop

🖼️ Example Usage: File Upload with Drag and Drop

🌍 Navigation and Scrolling Commands

🔄 navigate

📋 Parameters

🧪 Example Usage

⬇️ scroll

📋 Parameters

🧪 Example Usage

⬇️ scrollTo

📋 Parameters

🧪 Example Usage

🗂️ tab

📋 Parameters

🧪 Example Usage

Switch to a Specific Tab

Close a Specific Tab

Open a New Tab with a URL

Close the Current Tab

🖼️ switchToFrame

📋 Parameters

🧪 Example Usage

Switch to Frame by Locator:

Switch to Frame by Index:

✅ Assertions and Validation Commands

✅ assert

📋 Parameters

🧪 Example Usage: Assert by Attribute

🧪 Example Usage: Assert Multiple Elements

📸 image

📋 Parameters

🧪 Types of Image Comparisons

🧪 Example Usage: Full Screen Comparison

🧪 Example Usage: Compare with Highlighting Differences

🧪 Example Usage: Compare with Exclude Area

🧪 Example Usage: Compare Part of Screen

🧪 Example Usage: Compare an Image from the Page

⚙️ Utilities and Enhancements Commands

💻 javascript

📋 Parameters

🧪 Example Usage

⏳ wait

📋 Parameters

🧪 Example Usage

Wait for an Element to Become Clickable

🖱️ `click`

🖱️ `doubleClick`

📝 `input`

🧩 `dropDown`

🖱️ `hover`

⌨️ `hotKey`

🧹 `clear`

🏋️‍♀️ `dragAndDrop`

🔄 `navigate`

⬇️ `scroll`

⬇️ `scrollTo`

🗂️ `tab`

🖼️ `switchToFrame`

✅ `assert`

📸 `image`

💻 `javascript`

⏳ `wait`

🔄 `repeat`

➕ `include`