Why DOM interaction handles complex UIs in Cypress - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to select an element by its class using Cypress.

Cypress

cy.get('[1]')

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

A".button"

B"#button"

C"button"

D"[button]"

Attempts:

3 left

💡 Hint

Common Mistakes

Using '#' which selects by id instead of class.

Not using quotes around the selector.

In Cypress, to select an element by class, you use a dot before the class name inside quotes, like ".button".

2fill in blank

medium

Complete the code to click a button with id 'submit' using Cypress.

Cypress

cy.get('[1]').click()

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

A"#submit"

B".submit"

C"submit"

D"[submit]"

Attempts:

3 left

💡 Hint

Common Mistakes

Using '.' which selects by class instead of id.

Forgetting to add .click() after get.

To select an element by id in Cypress, use #idName. Here, #submit selects the element with id 'submit'.

3fill in blank

hard

Fix the error in the code to wait for an element with data-cy attribute 'login' before clicking.

Cypress

cy.get('[1]').click()

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

A"data-cy=login"

B"[data-cy=login]"

C"#data-cy=login"

D".data-cy=login"

Attempts:

3 left

💡 Hint

Common Mistakes

Missing square brackets around attribute selector.

Using '.' or '#' which are for class or id selectors.

To select elements by attribute in Cypress, use square brackets with the attribute and value inside quotes, like [data-cy=login].

4fill in blank

hard

Fill both blanks to assert that a button with class 'submit' is visible.

Cypress

cy.get('[1]').should('[2]')

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

A".submit"

B"be.visible"

C"be.enabled"

D"#submit"

Attempts:

3 left

💡 Hint

Common Mistakes

Using id selector instead of class.

Using 'be.enabled' instead of 'be.visible'.

Use cy.get('.submit') to select by class. The assertion should('be.visible') checks if the element is visible.

5fill in blank

hard

Fill all three blanks to create a test that types 'hello' into an input with id 'name', then asserts it has the correct value.

Cypress

cy.get('[1]').[2]('hello').should('[3]', 'hello')

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

A"#name"

Btype

Chave.value

Dclick

Attempts:

3 left

💡 Hint

Common Mistakes

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

Using wrong assertion like 'be.visible' instead of 'have.value'.

Select the input by id with #name. Use type('hello') to enter text. Then assert with should('have.value', 'hello').

Practice

1. Why is DOM interaction important when testing complex user interfaces with Cypress?

easy

A. It allows tests to directly control and check webpage elements as they change.

B. It makes tests run faster by skipping element checks.

C. It automatically fixes UI bugs during testing.

D. It prevents any changes in the webpage during tests.

Solution

1. Step 1: Understand DOM interaction role

   DOM interaction lets tests access and manipulate webpage elements directly, which is essential for dynamic UIs.

2. Step 2: Connect to complex UI needs

   Complex UIs change after user actions, so direct control helps tests verify these changes accurately.

3. Final Answer:

   It allows tests to directly control and check webpage elements as they change. -> Option A

4. Quick Check:

   DOM interaction = direct control and checking [OK]

Hint: Remember: DOM interaction means direct element control [OK]

Common Mistakes:

• Thinking DOM interaction speeds tests by skipping checks
• Believing it fixes bugs automatically
• Assuming it stops webpage changes during tests

2. Which Cypress command is used to select an element from the DOM for interaction?

easy

A. click()

B. get()

C. should()

D. visit()

Solution

1. Step 1: Identify command purpose

   The get() command selects elements from the DOM to interact with.

2. Step 2: Differentiate from other commands

   click() triggers clicks, should() asserts conditions, and visit() loads pages.

3. Final Answer:

   get() -> Option B

4. Quick Check:

   Element selection = get() [OK]

Hint: Use get() to pick elements before actions [OK]

Common Mistakes:

• Using click() to select elements
• Confusing should() with element selection
• Thinking visit() selects elements

3. Given the code:

cy.get('.btn').click().should('have.class', 'active')

What does this test check in a complex UI?

medium

A. The button with class 'btn' is clicked and then has class 'active'.

B. The button is clicked but should not have class 'active'.

C. The button is selected but not clicked.

D. The button is checked for visibility only.

Solution

1. Step 1: Analyze command chain

   cy.get('.btn') selects the button, click() clicks it, and should('have.class', 'active') asserts it has the 'active' class.

2. Step 2: Understand test purpose

   This checks that clicking the button changes its class to 'active', common in complex UIs.

3. Final Answer:

   The button with class 'btn' is clicked and then has class 'active'. -> Option A

4. Quick Check:

   Click then check class = correct test [OK]

Hint: Click then assert class change means success [OK]

Common Mistakes:

• Ignoring the click() effect
• Thinking should() checks absence of class
• Confusing selection with clicking

4. Identify the error in this Cypress code snippet for a complex UI:

cy.get('#submit').click.should('be.visible')

medium

A. 'should' cannot be chained after 'click'.

B. Incorrect selector syntax for 'get'.

C. Missing parentheses after 'click' command.

D. 'be.visible' is not a valid assertion.

Solution

1. Step 1: Check command syntax

   The click command requires parentheses: click().

2. Step 2: Verify chaining correctness

   With click() fixed, chaining should('be.visible') is valid to assert visibility.

3. Final Answer:

   Missing parentheses after 'click' command. -> Option C

4. Quick Check:

   click() needs parentheses [OK]

Hint: Always add () after commands like click [OK]

Common Mistakes:

• Omitting parentheses on commands
• Thinking selector syntax is wrong
• Believing should() can't follow click()

5. In a complex UI, a button initially has class 'disabled' and its class toggles between 'enabled' and 'disabled' after each click. Which Cypress code correctly tests this toggle behavior?

hard

A. cy.get('#toggleBtn').click().click().should('have.class', 'enabled')

B. cy.get('#toggleBtn').click().should('have.class', 'disabled').click().should('have.class', 'enabled')

C. cy.get('#toggleBtn').should('have.class', 'enabled').click().should('have.class', 'disabled')

D. cy.get('#toggleBtn').click().should('have.class', 'enabled').click().should('have.class', 'disabled')

Solution

1. Step 1: Understand toggle sequence

   The button starts with 'disabled', clicking toggles to 'enabled', then clicking again toggles back to 'disabled'.

2. Step 2: Match code to toggle logic

   cy.get('#toggleBtn').click().should('have.class', 'enabled').click().should('have.class', 'disabled') clicks once, checks 'enabled', clicks again, checks 'disabled', matching the toggle behavior.

3. Final Answer:

   cy.get('#toggleBtn').click().should('have.class', 'enabled').click().should('have.class', 'disabled') -> Option D

4. Quick Check:

   Click, check enabled, click, check disabled = correct toggle test [OK]

Hint: Test toggle by clicking and asserting classes in order [OK]

Common Mistakes:

• Reversing expected classes after clicks
• Missing initial class check
• Clicking twice before any assertion