Why Dual commands in Cypress? - Purpose & Use Cases

The Big Idea

What if you could click and check in one simple step, making testing faster and easier?

The Scenario

Imagine testing a web page where you need to click a button and then check if a message appears. Doing this manually means clicking, waiting, and watching carefully every time.

The Problem

Manually clicking and checking is slow and easy to miss mistakes. You might forget to wait for the message or click the wrong button. It's tiring and error-prone, especially when testing many pages.

The Solution

Dual commands in Cypress let you combine actions and checks in one smooth step. You can click a button and immediately verify the result without extra waits or steps. This makes tests faster and more reliable.

Before vs After

✗ Before

cy.get('#submit').click();
cy.get('#message').should('be.visible');

✓ After

cy.get('#submit').click().get('#message').should('be.visible');

What It Enables

Dual commands let you write clear, fast tests that do multiple things in one go, saving time and reducing mistakes.

Real Life Example

Testing a login form where clicking 'Login' shows a welcome message: dual commands let you click and check the message in one smooth step.

Key Takeaways

Manual testing is slow and easy to mess up.

Dual commands combine actions and checks for smoother tests.

This makes tests faster, clearer, and less error-prone.