Parent commands in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Cypress test snippet?

Consider the following Cypress test code. What will be the text content of the parentText variable after running?

Cypress

cy.get('ul#list > li.selected').parent().invoke('text').then(parentText => {
  cy.log(parentText);
});

A The text content of the <ul> element containing the selected <li>

B The text content of the selected <li> element only

C An empty string because <ul> has no text

D A JavaScript error because parent() is not a valid Cypress command

💡 Hint

Remember, parent() moves up one level in the DOM tree.

The parent() command selects the immediate parent element of the matched element(s). Here, it selects the ul#list element. Invoking text on it returns all text inside the

, including all
• children.

❓ assertion

intermediate

Which assertion correctly verifies the parent element's class?

You want to check that the parent of a button with id submitBtn has the class form-group. Which assertion is correct?

Cypress

cy.get('#submitBtn').parent()

A cy.get('#submitBtn').parent().should('contain', 'form-group')

B cy.get('#submitBtn').parent().should('have.class', 'form-group')

C cy.get('#submitBtn').parent().should('have.text', 'form-group')

D cy.get('#submitBtn').parent().should('have.attr', 'form-group')

💡 Hint

Use the correct assertion to check for a CSS class.

The have.class assertion checks if the element has the specified CSS class. Other options check for text content or attributes, which are incorrect here.

🔧 Debug

advanced

Why does this Cypress test fail to find the parent element?

Given this code, the test fails with Timed out retrying error. Why?

Cypress

cy.get('.child-element').parent('.nonexistent-class').should('exist');

A Because <code>parent()</code> only accepts no arguments; passing a selector causes failure

B Because <code>parent()</code> returns all ancestors, not just immediate parent

C Because <code>should('exist')</code> is invalid syntax

D Because the parent element does not have the class <code>nonexistent-class</code>, so the chain yields no elements

💡 Hint

Check if the parent element matches the selector passed to parent().

The parent() command can take a selector to filter the immediate parent. If the parent does not match, the result is empty, causing the should('exist') assertion to fail.

🧠 Conceptual

advanced

What is the difference between parent() and parents() in Cypress?

Choose the best explanation of how parent() and parents() differ in Cypress DOM traversal.

A <code>parent()</code> and <code>parents()</code> are aliases and behave identically

B <code>parent()</code> selects all ancestors; <code>parents()</code> selects only the immediate parent

C <code>parent()</code> selects the immediate parent; <code>parents()</code> selects all ancestors up to the root

D <code>parent()</code> selects siblings; <code>parents()</code> selects children

💡 Hint

Think about how many levels up each command goes.

parent() moves one level up to the immediate parent. parents() moves up all levels, returning all ancestors up to the document root.

❓ framework

expert

Which Cypress command chain correctly clicks a button's parent element and verifies its visibility?

Given a button with class btn-action, you want to click its parent element and then check if that parent is visible. Which command chain is correct?

A cy.get('.btn-action').parent().should('be.visible').click();

B cy.get('.btn-action').parent().click().should('be.visible');

C cy.get('.btn-action').click().parent().should('be.visible');

D cy.get('.btn-action').parent().click().should('exist');

💡 Hint

Remember Cypress commands are asynchronous and chainable; order matters.

Option A first gets the parent, asserts it is visible, then clicks it. This ensures the parent is visible before clicking. Option A clicks before asserting visibility, which may cause flaky tests. Option A clicks the button, then tries to get parent, which is invalid chaining. Option A asserts existence, not visibility.

Practice

1. What does the Cypress parent() command do?

easy

A. It finds the direct parent element of the current element.

B. It finds all child elements inside the current element.

C. It clicks on the current element.

D. It waits for the element to appear on the page.

Solution

1. Step 1: Understand the purpose of parent()

   The parent() command in Cypress is used to get the immediate parent of the selected element in the DOM tree.

2. Step 2: Compare with other options

   Options A, B, and D describe different commands or actions unrelated to parent(). Only It finds the direct parent element of the current element. correctly describes the direct parent selection.

3. Final Answer:

   It finds the direct parent element of the current element. -> Option A

4. Quick Check:

   parent() = direct parent element [OK]

Hint: Remember: parent() gets one level up in the DOM tree [OK]

Common Mistakes:

• Confusing parent() with children()
• Thinking parent() clicks the element
• Assuming parent() waits for elements

2. Which of the following is the correct syntax to get the parent of an element with class child-item in Cypress?

easy

A. cy.get('.child-item').children();

B. cy.get('.child-item').parents();

C. cy.get('.child-item').parent('.parent-item');

D. cy.get('.child-item').parent();

Solution

1. Step 1: Identify the basic parent command syntax

   The basic syntax to get the direct parent is cy.get(selector).parent();. This returns the immediate parent element.

2. Step 2: Analyze options

   cy.get('.child-item').parents(); uses parents() which gets all ancestors, not just the direct parent. cy.get('.child-item').parent('.parent-item'); filters the direct parent to only those matching '.parent-item', but the question does not specify the parent's class. cy.get('.child-item').children(); gets children, not parent.

3. Final Answer:

   cy.get('.child-item').parent(); -> Option D

4. Quick Check:

   Correct syntax = cy.get(...).parent() [OK]

Hint: Use parent() without arguments for direct parent [OK]

Common Mistakes:

• Using parents() instead of parent()
• Trying to pass selector directly inside parent() incorrectly
• Confusing children() with parent()

3. What will the following Cypress code select?

cy.get('.list-item').parent('.list-container').should('have.class', 'active');

medium

A. All parents of '.list-item' with class 'list-container' regardless of other classes.

B. The direct parent of '.list-item' that has class 'list-container' and also has class 'active'.

C. The child elements of '.list-item' with class 'active'.

D. The '.list-item' elements themselves if they have class 'active'.

Solution

1. Step 1: Understand the parent() with selector

   The parent('.list-container') command filters the direct parent to only those with class list-container.

2. Step 2: Understand the assertion

   The should('have.class', 'active') asserts that the selected parent element also has the class active.

3. Final Answer:

   The direct parent of '.list-item' that has class 'list-container' and also has class 'active'. -> Option B

4. Quick Check:

   parent(selector) filters direct parent [OK]

Hint: parent(selector) filters direct parent by selector [OK]

Common Mistakes:

• Thinking parents() selects only direct parent
• Confusing child elements with parent elements
• Ignoring the filter selector in parent()

4. You wrote this Cypress code but it fails:

cy.get('.button').parent('.container').click();

What is the likely cause of the failure?

medium

A. The parent element with class 'container' does not exist directly above '.button'.

B. The parent() command cannot be chained with click().

C. The selector '.button' is invalid.

D. You must use parents() instead of parent().

Solution

1. Step 1: Check the parent selector usage

   The parent('.container') filters the direct parent to only those with class 'container'. If no direct parent matches, the command yields no element.

2. Step 2: Understand why click() fails

   Since no element is found, click() fails because it has nothing to act on.

3. Final Answer:

   The parent element with class 'container' does not exist directly above '.button'. -> Option A

4. Quick Check:

   parent(selector) fails if no direct parent matches [OK]

Hint: Check if direct parent matches selector before chaining actions [OK]

Common Mistakes:

• Assuming parent() always finds an element
• Thinking click() can't chain after parent()
• Using parents() unnecessarily

5. You want to verify that a button with class submit-btn is inside a form with class user-form. Which Cypress code correctly checks the form is the direct parent of the button?

hard

A. cy.get('.user-form').children('.submit-btn').should('exist');

B. cy.get('.submit-btn').parents('form.user-form').should('exist');

C. cy.get('.submit-btn').parent('form.user-form').should('exist');

D. cy.get('.submit-btn').parent().should('have.class', 'user-form');

Solution

1. Step 1: Understand direct parent check

   To check if the direct parent matches a selector, use parent(selector). cy.get('.submit-btn').parent('form.user-form').should('exist'); uses this correctly.

2. Step 2: Compare other options

   cy.get('.submit-btn').parents('form.user-form').should('exist'); checks all ancestors, not just direct parent. cy.get('.user-form').children('.submit-btn').should('exist'); checks children of the form, reversed logic. cy.get('.submit-btn').parent().should('have.class', 'user-form'); checks parent but does not filter by selector, so it may pass incorrectly.

3. Final Answer:

   cy.get('.submit-btn').parent('form.user-form').should('exist'); -> Option C

4. Quick Check:

   parent(selector) verifies direct parent matches selector [OK]

Hint: Use parent(selector) to confirm direct parent matches [OK]

Common Mistakes:

• Using parents() when only direct parent matters
• Checking children instead of parent
• Not filtering parent by selector