Digital Shelf

Working with dynamic tables in end-to-end testing is a common but often tricky task — especially when rows are editable, contain checkboxes, or are updated live. This guide shows how to use Cypress to interact with rows based on both content and index , as well as how to perform validations across multiple rows dynamically. Example HTML Table Cypress Test Example Cypress Table Interaction Techniques Finding Rows by Text A simple and reliable way to work with table rows is to

Dropdowns in web applications can be implemented in different ways, and Cypress offers multiple strategies to work with them depending on the type of dropdown element used. Types of Dropdowns 1. Native HTML Dropdowns (<select> elements) These are standard HTML dropdowns using the <select> and <option> tags. How Cypress handles it: Use the .select() command to choose an option by its visible text or value. Cypress doesn't need to simulate opening the dropdown—it sets the value

Date pickers on Wix forms are custom components. The calendar doesn’t open with a simple input click — instead, it's triggered through a separate button and rendered inside a dynamic popup portal. I had to add wait() calls because there were issues opening the Wix calendar reliably. It’s a dynamic component, and there wasn’t much I could do without access to the page’s internal code. These waits help ensure the calendar is visible and stable before selecting a date. Test Exam

Cypress offers built-in commands for interacting with form inputs like checkboxes and radio buttons. Here's a practical guide for checking, unchecking, asserting, and even forcing actions — with clear examples taken from real-world usage. Interacting with Checkboxes Checking and Unchecking Use .check() and .uncheck() to toggle checkboxes. Cypress automatically asserts visibility and interactability — unless you override it. Working with Radio Buttons Cypress uses .check() to

In automated testing, it's often not enough to just click buttons — you need to verify that the content on the page is correct . Cypress makes it easy to extract values like: Label and button text Input values Attributes like placeholder, class, or id In this post, we’ll look at how to read, store, and assert text and attributes using Cypress, all based on the real login form on radeksto.com/test/login . Why Extract Values? Extracting values is essential when you want to: Va

In Cypress, you can save a selected DOM element (the subject ) using tools like: .as() – to give it a reusable alias .then() – to access and work with the raw DOM or jQuery element wrap() – to re-wrap a DOM element back into a Cypress chain We'll apply all of this using the actual elements from your working login page at: https://www.radeksto.com/test/login 1. Save an Element Using .as() You can assign any Cypress command result to an alias using .as('name'), and later refer