Why should() with chainers in Cypress? - Purpose & Use Cases

The Big Idea

What if you could check many things about a page element with just one simple command?

The Scenario

Imagine testing a website by clicking around and checking if elements look right, have the correct text, and behave as expected--all by eye and memory.

You try to remember if a button is visible, enabled, and has the right label, but it's easy to miss details or forget steps.

The Problem

Manually checking each condition is slow and tiring. You might miss bugs because your eyes get tired or you forget to check something.

Also, repeating these checks every time you update the site wastes time and causes frustration.

The Solution

The should() command with chainers in Cypress lets you write clear, simple tests that check many things about an element in one go.

This means you can quickly verify multiple conditions like visibility, text content, and CSS styles together, making tests easier to write and understand.

Before vs After

✗ Before

cy.get('button').should('be.visible')
cy.get('button').should('have.text', 'Submit')
cy.get('button').should('not.be.disabled')

✓ After

cy.get('button').should('be.visible').and('have.text', 'Submit').and('not.be.disabled')

What It Enables

You can write fast, readable tests that check many things at once, catching bugs early and saving time.

Real Life Example

When testing a login form, you want to confirm the submit button is visible, enabled, and says "Log In" before clicking it. Using should() with chainers makes this easy and reliable.

Key Takeaways

Manual checks are slow and error-prone.

should() with chainers lets you combine many checks in one statement.

This makes tests faster, clearer, and more reliable.

Practice

1. What does the should() command do in Cypress testing?

easy

A. It asserts that the selected element meets a specific condition.

B. It clicks on the selected element.

C. It waits for the page to load completely.

D. It navigates to a new URL.

Solution

1. Step 1: Understand the purpose of should()

   The should() command is used to check if an element meets a condition, like visibility or text content.

2. Step 2: Differentiate from other commands

   Commands like clicking or navigation are done by other Cypress commands, not should().

3. Final Answer:

   It asserts that the selected element meets a specific condition. -> Option A

4. Quick Check:

   should() = assertion [OK]

Hint: Remember: should() checks conditions, it doesn't perform actions [OK]

Common Mistakes:

• Confusing should() with click() or visit()
• Thinking should() changes page state
• Using should() without a condition

2. Which of the following is the correct syntax to check if an element is visible and contains the text 'Submit' using should() with chaining?

easy

A. cy.get('button').should('visible', 'Submit')

B. cy.get('button').should('be.visible', 'contain', 'Submit')

C. cy.get('button').should('contain', 'Submit').should('visible')

D. cy.get('button').should('be.visible').and('contain', 'Submit')

Solution

1. Step 1: Identify correct chaining syntax

   The correct way is to use should() for the first assertion and and() for chaining additional assertions.

2. Step 2: Check each option

   cy.get('button').should('be.visible').and('contain', 'Submit') uses should('be.visible') then and('contain', 'Submit'), which is correct syntax. Others misuse parameters or chaining.

3. Final Answer:

   cy.get('button').should('be.visible').and('contain', 'Submit') -> Option D

4. Quick Check:

   Use should() then and() for multiple checks [OK]

Hint: Use should() first, then and() to chain assertions [OK]

Common Mistakes:

• Passing multiple conditions in one should() call incorrectly
• Using should() multiple times instead of and()
• Wrong order of chaining

3. What will be the result of the following Cypress code?

cy.get('input').should('have.attr', 'type').and('eq', 'text')

medium

A. The test throws a syntax error.

B. The test passes if the input element has a type attribute equal to 'text'.

C. The test passes if the input element has any type attribute, regardless of value.

D. The test fails if the input element has any type attribute.

Solution

1. Step 1: Understand the first assertion

   should('have.attr', 'type') checks if the element has a 'type' attribute.

2. Step 2: Understand the chained assertion

   and('eq', 'text') checks if the attribute's value equals 'text'. Both must be true for the test to pass.

3. Final Answer:

   The test passes if the input element has a type attribute equal to 'text'. -> Option B

4. Quick Check:

   have.attr + eq chaining = attribute equals value [OK]

Hint: Chain have.attr with eq to check attribute value [OK]

Common Mistakes:

• Thinking have.attr only checks presence, not value
• Confusing eq with contain
• Assuming syntax error due to chaining

4. Identify the error in this Cypress test code:

cy.get('button').should('be.visible').and('contain', Submit)

medium

A. The selector 'button' is invalid.

B. The chaining with and() is not allowed after should().

C. The text 'Submit' should be a string inside quotes.

D. The should() command cannot check visibility.

Solution

1. Step 1: Check the parameter passed to contain

   The word Submit is not in quotes, so it is treated as a variable, which causes an error.

2. Step 2: Verify chaining and selector

   Chaining with and() is valid, and 'button' is a valid selector. should('be.visible') is also valid.

3. Final Answer:

   The text 'Submit' should be a string inside quotes. -> Option C

4. Quick Check:

   Text values must be quoted in assertions [OK]

Hint: Always quote text strings in should() and and() assertions [OK]

Common Mistakes:

• Forgetting quotes around text in contain
• Thinking and() chaining is invalid
• Misunderstanding selector syntax

5. You want to verify that a checkbox is checked and also has the attribute 'disabled' set to true. Which Cypress command chain correctly performs both checks?

hard

A. cy.get('input[type=checkbox]').should('be.checked').and('have.attr', 'disabled', 'true')

B. cy.get('input[type=checkbox]').should('have.attr', 'disabled', 'true').should('checked')

C. cy.get('input[type=checkbox]').should('be.checked', 'have.attr', 'disabled', 'true')

D. cy.get('input[type=checkbox]').and('be.checked').and('have.attr', 'disabled', 'true')

Solution

1. Step 1: Understand chaining with should() and and()

   Use should() for the first assertion and and() to chain the second assertion.

2. Step 2: Check each option's correctness

   cy.get('input[type=checkbox]').should('be.checked').and('have.attr', 'disabled', 'true') correctly chains should('be.checked') and and('have.attr', 'disabled', 'true'). cy.get('input[type=checkbox]').should('have.attr', 'disabled', 'true').should('checked') uses invalid chainer should('checked') instead of should('be.checked'). cy.get('input[type=checkbox]').should('be.checked', 'have.attr', 'disabled', 'true') incorrectly passes multiple conditions in one should(). cy.get('input[type=checkbox]').and('be.checked').and('have.attr', 'disabled', 'true') uses and() without should() first, which is invalid.

3. Final Answer:

   cy.get('input[type=checkbox]').should('be.checked').and('have.attr', 'disabled', 'true') -> Option A

4. Quick Check:

   should() then and() for multiple assertions [OK]

Hint: Start with should(), then chain with and() for multiple checks [OK]

Common Mistakes:

• Passing multiple conditions in one should() call
• Using and() without should() first
• Using multiple should() calls unnecessarily