Multiple assertions chaining in Cypress - Test Execution Trace

Test Overview

This test opens a webpage, finds a button, clicks it, and then checks multiple things about a message that appears. It verifies the message is visible, has the correct text, and has the right CSS color.

Test Code - Cypress

Cypress

describe('Multiple assertions chaining test', () => {
  it('checks message visibility, text, and color after button click', () => {
    cy.visit('https://example.cypress.io')
    cy.get('#show-message-btn').click()
    cy.get('#message')
      .should('be.visible')
      .and('have.text', 'Hello, Cypress!')
      .and('have.css', 'color', 'rgb(0, 128, 0)')
  })
})

Execution Trace - 9 Steps

Step	Action	System State	Assertion	Result
1	Test starts	Test runner is ready to execute the test	—	PASS
2	Browser opens and navigates to 'https://example.cypress.io'	The example Cypress page is loaded in the browser	—	PASS
3	Find element with id 'show-message-btn' using cy.get	Button with id 'show-message-btn' is found on the page	—	PASS
4	Click the button '#show-message-btn'	Button is clicked, triggering message display	—	PASS
5	Find element with id 'message' using cy.get	Message element is present in the DOM	—	PASS
6	Assert the message is visible using .should('be.visible')	Message is visible on the page	Message visibility is true	PASS
7	Assert the message text is 'Hello, Cypress!' using .and('have.text', ...)	Message text content is 'Hello, Cypress!'	Message text matches expected	PASS
8	Assert the message CSS color is 'rgb(0, 128, 0)' using .and('have.css', ...)	Message color style is green (rgb(0, 128, 0))	Message color matches expected	PASS
9	Test ends successfully	All assertions passed, test completed	—	PASS

Failure Scenario

Failing Condition: The message element is not visible, or text/color does not match expected values

Execution Trace Quiz - 3 Questions

What does the test check after clicking the button?

A That the message is visible, has correct text, and correct color

B That the button disappears

C That the page URL changes

D That an alert pops up

Key Result

Chaining multiple assertions on the same element in Cypress makes tests concise and readable while verifying several properties in one go.

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