Multiple assertions chaining in Cypress - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does chaining multiple assertions in Cypress mean?

It means writing several checks one after another on the same element or subject, so you can verify many things in a clean and readable way.

beginner

How do you chain assertions in Cypress?

You use dot notation to add multiple should() or and() commands after selecting an element, like cy.get('button').should('be.visible').and('contain', 'Submit').

beginner

Why is chaining assertions useful in tests?

It keeps tests simple and easy to read, reduces repeated code, and ensures all related checks happen on the same element without extra lookups.

beginner

Example: What does this Cypress code check?
cy.get('input').should('be.visible').and('have.attr', 'type', 'text')

It checks that the input field is visible on the page and that it has an attribute type with the value text.

intermediate

Can you chain different types of assertions in Cypress?

Yes, you can chain assertions that check visibility, content, attributes, CSS styles, and more, all in one chain.

Which command is used to chain multiple assertions in Cypress?

A should() and and()

B expect() and verify()

C assert() and check()

D test() and run()

In Cypress, should() and and() are used to chain multiple assertions on the same element.

What is the benefit of chaining assertions in Cypress tests?

A Runs tests faster by skipping checks

B Automatically fixes failed tests

C Makes tests easier to read and reduces repeated code

D Allows testing multiple pages at once

Chaining assertions keeps tests clean and readable and avoids repeating element lookups.

Which of these is a valid chained assertion in Cypress?

A cy.get('div').test('exist').run('visible')

B cy.get('div').check('exist').then('visible')

C cy.get('div').assert('exist').verify('visible')

D cy.get('div').should('exist').and('be.visible')

Only should() and and() are valid for chaining assertions in Cypress.

What happens if one assertion in a chain fails in Cypress?

A The whole test fails immediately

B The test ignores the failure and continues

C Only that assertion is skipped

D The test retries the assertion automatically

If any assertion in the chain fails, Cypress stops and marks the test as failed.

Which is the best practice for chaining assertions in Cypress?

A Chain assertions on different elements in one chain

B Chain assertions on the same element to keep tests clear

C Avoid chaining and write separate tests for each check

D Use chaining only for CSS style checks

Chaining assertions on the same element improves readability and efficiency.

Explain how to chain multiple assertions in Cypress and why it is useful.

Think about how you check many things about one button in one go.

Describe what happens when one assertion in a chained Cypress command fails during test execution.

Consider how Cypress treats failed checks to keep tests reliable.

Practice

1. What is the main benefit of chaining multiple assertions with .should() and .and() in Cypress?

easy

A. It allows checking several conditions on the same element in one statement.

B. It runs tests faster by skipping some assertions.

C. It automatically fixes failing tests.

D. It changes the element's properties during the test.

Solution

1. Step 1: Understand chaining purpose

   Chaining .should() and .and() lets you check multiple things on one element without repeating the element selection.

2. Step 2: Identify benefit

   This makes tests shorter and clearer by combining checks in one statement.

3. Final Answer:

   It allows checking several conditions on the same element in one statement. -> Option A

4. Quick Check:

   Multiple assertions chaining = check many conditions [OK]

Hint: Use .should() once, then .and() for extra checks [OK]

Common Mistakes:

• Thinking chaining skips assertions
• Believing chaining changes element state
• Confusing chaining with test speedup

2. Which of the following is the correct syntax to check that an element is visible and contains text 'Hello' using chaining in Cypress?

easy

A. cy.get('button').should('contain.text', 'Hello').should('be.visible')

B. cy.get('button').and('be.visible').should('contain.text', 'Hello')

C. cy.get('button').should('be.visible').and('contain.text', 'Hello')

D. cy.get('button').and('contain.text', 'Hello').and('be.visible')

Solution

1. Step 1: Check chaining order

   The first assertion must use .should(), then additional checks use .and().

2. Step 2: Validate syntax correctness

   cy.get('button').should('be.visible').and('contain.text', 'Hello') correctly uses .should('be.visible') then .and('contain.text', 'Hello'). Options B and D wrongly start with .and(). cy.get('button').should('contain.text', 'Hello').should('be.visible') uses two .should() but chaining prefers .and() after first .should().

3. Final Answer:

   cy.get('button').should('be.visible').and('contain.text', 'Hello') -> Option C

4. Quick Check:

   First .should(), then .and() [OK]

Hint: Start with .should(), add checks with .and() [OK]

Common Mistakes:

• Starting chain with .and() instead of .should()
• Using multiple .should() instead of .and()
• Mixing order of assertions incorrectly

3. What will be the result of this Cypress code snippet?

cy.get('#login').should('be.visible').and('have.class', 'active').and('contain.text', 'Login')

medium

A. Test throws syntax error due to chaining.

B. Test fails if element #login is visible but missing class 'active'.

C. Test passes even if element #login is not visible.

D. Test passes if element #login is visible, has class 'active', and contains text 'Login'.

Solution

1. Step 1: Understand chained assertions

   The code checks three things on element with id 'login': visibility, class presence, and text content.

2. Step 2: Determine test pass/fail conditions

   All three conditions must be true for the test to pass. If any fail, test fails. Syntax is correct.

3. Final Answer:

   Test passes if element #login is visible, has class 'active', and contains text 'Login'. -> Option D

4. Quick Check:

   All chained assertions must pass [OK]

Hint: All chained assertions must be true for pass [OK]

Common Mistakes:

• Assuming test passes if only some assertions pass
• Thinking chaining causes syntax error
• Ignoring visibility check importance

4. Identify the error in this Cypress code snippet:

cy.get('.btn').and('be.enabled').should('have.text', 'Submit')

medium

A. Using .and() before .should() causes a syntax error.

B. The selector '.btn' is invalid.

C. The assertion 'have.text' is not supported.

D. No error; code is correct.

Solution

1. Step 1: Check chaining order

   Chaining must start with .should(). Using .and() first is invalid syntax.

2. Step 2: Validate other parts

   Selector '.btn' is valid CSS class selector. 'have.text' is a valid assertion. So no error there.

3. Final Answer:

   Using .and() before .should() causes a syntax error. -> Option A

4. Quick Check:

   Start chain with .should(), not .and() [OK]

Hint: Always start assertions with .should() [OK]

Common Mistakes:

• Starting chain with .and()
• Confusing selector syntax
• Misunderstanding assertion names

5. You want to verify a form input with id 'email' is visible, enabled, has placeholder 'Enter email', and is empty. Which chained assertions correctly achieve this?

hard

A. cy.get('#email').should('be.enabled').should('be.visible').should('have.attr', 'placeholder', 'Enter email').should('have.value', '')

B. cy.get('#email').should('be.visible').and('be.enabled').and('have.attr', 'placeholder', 'Enter email').and('have.value', '')

C. cy.get('#email').and('be.visible').and('be.enabled').and('have.attr', 'placeholder', 'Enter email').and('have.value', '')

D. cy.get('#email').should('have.value', '').should('be.visible').should('be.enabled').should('have.attr', 'placeholder', 'Enter email')

Solution

1. Step 1: Confirm chaining syntax

   Chaining must start with .should() and continue with .and() for multiple assertions on the same element.

2. Step 2: Check assertion order and correctness

   cy.get('#email').should('be.visible').and('be.enabled').and('have.attr', 'placeholder', 'Enter email').and('have.value', '') starts with .should('be.visible') then chains .and() for other checks. cy.get('#email').should('have.value', '').should('be.visible').should('be.enabled').should('have.attr', 'placeholder', 'Enter email') uses multiple .should() starting with value check, which is allowed but less concise and best practice is to start with visibility. cy.get('#email').and('be.visible').and('be.enabled').and('have.attr', 'placeholder', 'Enter email').and('have.value', '') incorrectly starts with .and(). cy.get('#email').should('be.enabled').should('be.visible').should('have.attr', 'placeholder', 'Enter email').should('have.value', '') uses multiple .should() which is allowed but less concise.

3. Final Answer:

   cy.get('#email').should('be.visible').and('be.enabled').and('have.attr', 'placeholder', 'Enter email').and('have.value', '') -> Option B

4. Quick Check:

   Start with .should(), chain with .and() for clarity [OK]

Hint: Start with .should('be.visible'), then chain .and() [OK]

Common Mistakes:

• Starting chain with .and()
• Using multiple .should() instead of chaining
• Ignoring assertion order for readability