Why patterns scale test suites in Cypress - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to visit the homepage in Cypress.

Cypress

cy.[1]('https://example.com')

Drag options to blanks, or click blank then click option'

Avisit

Bclick

Ctype

Dget

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'click' or 'get' instead of 'visit' to load a page.

The visit command loads a page in Cypress. Other commands like click or type interact with elements but do not load pages.

2fill in blank

medium

Complete the code to assert that a button with id 'submit' is visible.

Cypress

cy.get('#submit').[1]('be.visible')

Drag options to blanks, or click blank then click option'

Acontains

Bclick

Ctype

Dshould

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'click' or 'type' instead of 'should' for assertions.

The should command is used to make assertions in Cypress. Here, it checks if the button is visible.

3fill in blank

hard

Fix the error in the code to correctly select all list items inside a <ul> with class 'menu'.

Cypress

cy.get('ul.menu [1] li')

Drag options to blanks, or click blank then click option'

A#

B>

C.

D*

Attempts:

3 left

💡 Hint

Common Mistakes

Using '#' or '.' which select by id or class, not child elements.

The > selector selects direct children. To get all li inside ul.menu, use ul.menu > li.

4fill in blank

hard

Fill both blanks to create a reusable function that checks if an element with given selector contains expected text.

Cypress

function checkText(selector, text) {
  cy.get([1]).should([2], text)
}

Drag options to blanks, or click blank then click option'

Aselector

B'contain'

C'contain.text'

D'contains'

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong assertion like 'contains' which is a command, not an assertion here.

The function uses the selector parameter to get the element. The assertion uses should('contain', text) to check if the element contains the text.

5fill in blank

hard

Fill all three blanks to create a test that visits a page, types in an input, and asserts the input value.

Cypress

describe('Input test', () => {
  it('types and checks input', () => {
    cy.[1]('https://example.com/form')
    cy.get('#name').[2]('Alice')
    cy.get('#name').should([3], 'Alice')
  })
})

Drag options to blanks, or click blank then click option'

Avisit

Btype

C'have.value'

Dclick

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'click' instead of 'type' to enter text.

Using wrong assertion like 'contain' instead of 'have.value'.

The test visits the page with visit, types 'Alice' into the input with type, and asserts the input's value with should('have.value', 'Alice').

Practice

1. Why do patterns help when you have many tests in a Cypress test suite?

easy

A. They make tests run slower but more detailed.

B. They keep tests organized and easier to maintain.

C. They remove the need for assertions in tests.

D. They force tests to use only one browser.

Solution

1. Step 1: Understand test suite growth

   As test suites grow, managing many tests becomes harder without structure.

2. Step 2: Role of patterns in organization

   Patterns provide a clear structure, making tests easier to read and update.

3. Final Answer:

   They keep tests organized and easier to maintain. -> Option B

4. Quick Check:

   Patterns = organization and maintainability [OK]

Hint: Patterns organize tests for easier maintenance [OK]

Common Mistakes:

• Thinking patterns slow down tests
• Believing patterns remove assertions
• Assuming patterns limit browser choice

2. Which of the following is the correct way to reuse code in Cypress tests using patterns?

easy

A. Write all test steps inside one big test.

B. Copy and paste the same code in every test.

C. Create custom commands or functions to reuse code.

D. Avoid using functions to keep tests simple.

Solution

1. Step 1: Identify code reuse methods

   Copy-pasting repeats code and causes errors; functions/custom commands avoid this.

2. Step 2: Use Cypress features for reuse

   Cypress supports custom commands and helper functions to reuse code cleanly.

3. Final Answer:

   Create custom commands or functions to reuse code. -> Option C

4. Quick Check:

   Code reuse = custom commands/functions [OK]

Hint: Use custom commands to reuse code in Cypress [OK]

Common Mistakes:

• Copy-pasting code instead of reusing
• Writing one large test instead of small ones
• Avoiding functions thinking they complicate tests

3. Given this Cypress test snippet using a pattern:

cy.get('.btn').click()
cy.get('.input').type('hello')
cy.get('.btn').click()

What is a benefit of using a pattern to avoid repeating cy.get('.btn').click() twice?

medium

A. It reduces code duplication and makes maintenance easier.

B. It hides errors from the test report.

C. It causes the test to fail because of missing clicks.

D. It makes the test run twice as slow.

Solution

1. Step 1: Identify repeated code

   The command cy.get('.btn').click() appears twice, repeating code.

2. Step 2: Understand pattern benefits

   Using a pattern like a helper function avoids repetition, easing updates and reducing mistakes.

3. Final Answer:

   It reduces code duplication and makes maintenance easier. -> Option A

4. Quick Check:

   Patterns reduce duplication = easier maintenance [OK]

Hint: Patterns reduce repeated code for easier fixes [OK]

Common Mistakes:

• Thinking patterns slow tests
• Believing patterns hide errors
• Assuming repeated code is harmless

4. You have this Cypress test code with a pattern:

function clickButton() {
  cy.get('.btn').click()
}

clickButton()
clickButton()

But the test fails because the button is disabled after the first click. What is the best fix using patterns?

medium

A. Remove the second call to clickButton().

B. Add a wait between clicks to let the button enable again.

C. Ignore the error and keep the code as is.

D. Change the pattern to check if the button is enabled before clicking.

Solution

1. Step 1: Identify the problem with the pattern

   The pattern blindly clicks the button twice, but the button disables after first click.

2. Step 2: Improve the pattern for reliability

   Modify the pattern to check if the button is enabled before clicking to avoid errors.

3. Final Answer:

   Change the pattern to check if the button is enabled before clicking. -> Option D

4. Quick Check:

   Pattern fix = add condition check before action [OK]

Hint: Add checks in patterns to avoid disabled element errors [OK]

Common Mistakes:

• Removing needed test steps
• Using fixed waits causing flaky tests
• Ignoring errors instead of fixing patterns

5. You want to scale your Cypress test suite for a large app. Which pattern combination best helps keep tests fast, maintainable, and easy to update?

hard

A. Use page objects for selectors, custom commands for repeated actions, and fixtures for test data.

B. Write all tests in one file with repeated code for clarity.

C. Avoid using custom commands to keep tests simple and short.

D. Use only inline selectors and no helper functions.

Solution

1. Step 1: Identify patterns for scaling

   Page objects organize selectors, custom commands reuse actions, fixtures manage test data cleanly.

2. Step 2: Understand benefits of combining patterns

   Combining these patterns reduces duplication, improves readability, and speeds up maintenance.

3. Final Answer:

   Use page objects for selectors, custom commands for repeated actions, and fixtures for test data. -> Option A

4. Quick Check:

   Combine patterns = faster, maintainable tests [OK]

Hint: Combine page objects, commands, fixtures for scalable tests [OK]

Common Mistakes:

• Putting all tests in one file
• Avoiding helpers thinking they add complexity
• Using only inline selectors causing duplication