should() with chainers in Cypress - Build an Automation Script

Verify multiple properties of a button using should() with chainers

Preconditions (1)

Step 1: Locate the button with id 'submit-btn'

Step 2: Verify the button is visible

Step 3: Verify the button is enabled

Step 4: Verify the button has the text 'Submit'

✅ Expected Result: The button is visible, enabled, and displays the text 'Submit'

Automation Requirements - Cypress

Assertions Needed:

Verify element visibility

Verify element enabled state

Verify element text content

Best Practices:

Use should() with multiple chainers for concise assertions

Use data-cy or id selectors for stable element targeting

Avoid hardcoded waits; rely on Cypress automatic waits

Automated Solution

Cypress

describe('Button properties test', () => {
  beforeEach(() => {
    cy.visit('https://example.com/sample-page')
  })

  it('should verify button visibility, enabled state, and text using should() with chainers', () => {
    cy.get('#submit-btn')
      .should('be.visible')
      .and('be.enabled')
      .and('have.text', 'Submit')
  })
})

The test visits the sample page before each test to ensure a fresh state.

It locates the button using its id #submit-btn, which is a stable selector.

The should() command is used with multiple chainers: be.visible to check visibility, be.enabled to check if the button is enabled, and have.text to verify the button's text content.

This chaining makes the test concise and easy to read.

Cypress automatically waits for elements to appear, so no explicit waits are needed.

Common Mistakes - 3 Pitfalls

Using multiple separate should() calls instead of chaining

Using unstable selectors like classes that change frequently

Using hardcoded waits like cy.wait(5000)

Bonus Challenge

Now add data-driven testing to verify the button text for three different buttons with ids 'submit-btn', 'cancel-btn', and 'reset-btn' and their expected texts 'Submit', 'Cancel', and 'Reset' respectively.

Show Hint

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