Div

The Div class provides a clean interface for interacting with generic container elements such as <div> blocks. It includes methods for selection, assertions, and scrolling into view.

Usage : div

🧩 Code

The Div class is designed to interact with common div element

To insert a code block with syntax highlighting:

Cypress

import { oi } from "@ordino.ai/spartify-engine";

oi.ui.div(this.div_element).click()

Playwright

Methods

click(): void Simulates a click on the div element.

• @returns void

Cypress

oi.ui.div(this.element).click()

Playwright

forceClick(): void Forces a click on the div element, bypassing any potential blockers.

• @returns void

Cypress

oi.ui.div(this.element).forceClick()

Playwright

doubleClick(forceClick: boolean): void Simulates a double-click on the div element.

• @param {force} – true (optional)

• @returns void

Cypress

oi.ui.div(this.element).doubleClick(true)

Playwright

rightClick(): void Simulates a right-click on the div element.

• @param {force} – true (optional)

• @returns void

Cypress

oi.ui.div(this.element).rightClick(true)

Playwright

clickDivWithCoordinates(x: number, y: number,forceClick:boolean): void Simulates a click on the div element at the specified coordinates.

• @param {x} – The x-coordinate for the click.

• @param {y} – The y-coordinate for the click.

• @param {force} – { force: true } optional

• @returns void

Cypress

oi.ui.div(this.element).clickDivWithCoordinates(1,2,true)

Playwright

centerClick(forceClick: boolean): void Simulates a click on the center of the div element.

• @param {force} – true (optional)

• @returns void

Cypress

oi.ui.div(this.element).centerClick(true)

Playwright

multiElementClick(forceClick: boolean): void Simulates a click on multiple div elements.

• @param {force} – true (optional)

• @returns void

Cypress

oi.ui.div(this.element).multiElementClick(true)

Playwright

firstElementClick(forceClick: boolean): void Simulates a click on the first div element in a collection.

• @param {force} – true (optional)

• @returns void

Cypress

oi.ui.div(this.element).firstElementClick(true)

Playwright

lastElementClick(forceClick: boolean): void Simulates a click on the last div element in a collection

• @param {force} – true (optional)

• @returns void

Cypress

oi.ui.div(this.element).lastElementClick(true)

Playwright

getDivText(): void Retrieves the text content of the div element.

• @returns void

Cypress

oi.ui.div(this.element).getDivText()

Playwright

Assertions

isEnabled(): void Asserts that the div element is enabled

• @returns trueif the div is enable, otherwise false.

Cypress

oi.ui.div(this.element).isEnabled()

Playwright

isDisabled(): void Asserts that the div element is disabled

• @returns trueif the div is enable, otherwise false.

Cypress

oi.ui.div(this.element).isDisabled()

Playwright

isDisplayed(): void Asserts that the div element is displayed

• @returns trueif the div is enable, otherwise false.

Cypress

oi.ui.div(this.element).isDisplayed()

Playwright

isFocused(): void Asserts that the div element is focused

• @returns trueif the div is enable, otherwise false.

Cypress

oi.ui.div(this.element).isFocused()

Playwright

assertDivIsVisible(): boolean Asserts that the div element is visible.

• @returns trueif the div is visible, otherwise false.

Cypress

oi.ui.div(this.element).asseertDivIsVisible()

Playwright

assertDivIsNotVisible(): boolean Asserts that the div element is not visible.

• @returns trueif the div is visible, otherwise false.

Cypress

oi.ui.div(this.element).assertDivIsNotVisible()

Playwright

assertDivIsEmpty(): boolean Asserts that the div element is empty.

• @returns trueif the div is visible, otherwise false.

Cypress

oi.ui.div(this.element).assertDivIsEmpty()

Playwright

Scrolling

scrollUntill(): void Scrolls until the div element is in view.

• @returns void

Cypress

oi.ui.div(this.element).scrollUntill()

Playwright

Custom Events

Ordino allows you to build custom actions or user journeys by directly interacting with the underlying tool’s native methods and actions.

This approach gives you full control, bypassing Ordino’s abstraction layer, and ensures you can leverage tool-specific capabilities as needed.

• locator → The element locator (e.g., XPath, CSS selector, or tool-specific reference).

• Returns → A tool element object on which you can invoke native actions (e.g., .click(), .type()).

// Generic pattern
element(locator): object

_{Ordino Custom Mode}

Using Ordino’s direct tool method reference:

// Ordino direct-to-tool approach
oi.ui.element('@xpath').click()

Here, Ordino will call the Cypress (or other tool) element object directly, rather than going through Ordino’s wrapper.

Building User Journeys

By chaining multiple oi.ui.element() calls, you can construct full user journeys while still working with native tool methods.

Example: Login Flow

// Enter username
oi.ui.element('//input[@id="username"]').type('testuser')

// Enter password
oi.ui.element('//input[@id="password"]').type('secret')

// Click login button
oi.ui.element('(//*[contains(text(),"Login")])[1]').click()

---

Key Notes

• Use this mode when you need maximum control over the test framework.

• This does not abstract or transform the call – it executes directly on the tool object (e.g., Cypress, Playwright, etc.).

• Perfect for custom journeys, advanced locators, or tool-specific actions not exposed by Ordino’s higher-level API.