cy.parent() and cy.children() in Cypress - Build an Automation Script

Verify parent and children elements using cy.parent() and cy.children()

Preconditions (2)

Step 1: Visit the web page at 'http://localhost:3000/menu'.

Step 2: Locate the <ul> element with id 'menu'.

Step 3: Use cy.children() on the <ul> element to get all <li> children.

Step 4: Assert that there are exactly 3 <li> children.

Step 5: Select the first <li> child and use cy.parent() to get its parent element.

Step 6: Assert that the parent element has id 'menu'.

✅ Expected Result: The test confirms that the <ul> element has exactly 3 <li> children and that the parent of the first <li> is the <ul> with id 'menu'.

Automation Requirements - Cypress

Assertions Needed:

Assert the number of children elements is 3

Assert the parent element has the correct id attribute

Best Practices:

Use cy.get() with id selector for locating elements

Chain commands properly to maintain readability

Use should() for assertions

Avoid hardcoding XPath selectors

Use descriptive test names

Automated Solution

Cypress

describe('Test cy.parent() and cy.children()', () => {
  it('should verify parent and children elements correctly', () => {
    cy.visit('http://localhost:3000/menu');

    // Get the <ul> element with id 'menu'
    cy.get('#menu')
      // Get all <li> children
      .children('li')
      // Assert there are exactly 3 children
      .should('have.length', 3)
      // Select the first <li> child
      .first()
      // Get its parent element
      .parent()
      // Assert the parent has id 'menu'
      .should('have.id', 'menu');
  });
});

The test starts by visiting the target page with cy.visit(). Then it locates the <ul> element by its id menu using cy.get('#menu'). Next, cy.children('li') fetches all <li> child elements of the <ul>. We assert that there are exactly 3 children using should('have.length', 3). Then, we select the first child with first() and get its parent element using cy.parent(). Finally, we assert that the parent element has the id menu with should('have.id', 'menu'). This confirms the parent-child relationship is correct.

Common Mistakes - 4 Pitfalls

Using cy.parent() on the parent element itself

{'mistake': 'Using cy.children() without specifying the child selector', 'why_bad': 'cy.children() returns all direct children, which may include unwanted elements, leading to flaky tests.', 'correct_approach': "Use cy.children('li') or the specific child selector to target only relevant children."}

{'mistake': 'Hardcoding XPath selectors instead of using id or class selectors', 'why_bad': 'XPath selectors are brittle and harder to maintain compared to CSS selectors like ids or classes.', 'correct_approach': "Use cy.get('#id') or cy.get('.class') for stable and readable selectors."}

Not chaining commands properly, causing timing issues

Bonus Challenge

Now add data-driven testing to verify parent and children for three different menu structures with varying number of <li> items.

Show Hint

Practice

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

easy

A. Finds all child elements of the current element

B. Finds the immediate parent element of the current element

C. Finds all sibling elements of the current element

D. Finds the first child element of the current element

Solution

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

   This command is used to get the immediate parent of the currently selected element in the DOM tree.

2. Step 2: Compare with other options

   cy.children() finds children, siblings are not targeted by cy.parent(), and it does not find the first child specifically.

3. Final Answer:

   Finds the immediate parent element of the current element -> Option B

4. Quick Check:

   cy.parent() = immediate parent [OK]

Hint: Parent means one level up in the DOM tree [OK]

Common Mistakes:

• Confusing parent with children
• Thinking it finds all ancestors
• Assuming it finds siblings

2. Which of the following is the correct syntax to get all direct children of an element with class container in Cypress?

easy

A. cy.get('.container').children()

B. cy.get('.container').parent()

C. cy.get('.container').child()

D. cy.get('.container').parents()

Solution

1. Step 1: Identify the correct command for children

   The command to get direct children is children(), so cy.get('.container').children() is correct.

2. Step 2: Check other options for correctness

   parent() gets the parent, child() is not a valid Cypress command, and parents() gets all ancestors, not children.

3. Final Answer:

   cy.get('.container').children() -> Option A

4. Quick Check:

   children() gets direct children [OK]

Hint: Use children() to get direct children elements [OK]

Common Mistakes:

• Using parent() instead of children()
• Using incorrect method child()
• Confusing parents() with children()

3. Consider the following HTML structure:

<div class='grandparent'>
  <div class='parent'>
    <span class='child'>Hello</span>
    <span class='child'>World</span>
  </div>
</div>

What will cy.get('.child').parent().should('have.class', 'parent') assert?

medium

A. That the grandparent has class 'parent'

B. That the children of .parent have class 'child'

C. That the parent of each .child element has class 'parent'

D. That the .child elements have class 'parent'

Solution

1. Step 1: Understand the command chain

   cy.get('.child') selects both span elements. parent() gets their immediate parent, which is the div with class 'parent'.

2. Step 2: Analyze the assertion

   The assertion checks if the parent element has class 'parent', which is true for both .child elements.

3. Final Answer:

   That the parent of each .child element has class 'parent' -> Option C

4. Quick Check:

   parent() gets immediate parent with class 'parent' [OK]

Hint: parent() gets immediate parent element of selected children [OK]

Common Mistakes:

• Thinking parent() gets grandparent
• Confusing children with parent
• Assuming assertion checks children classes

4. You wrote this Cypress test:

cy.get('.list').children('.item').parent('.container')

But it fails with an error. What is the likely cause?

medium

A. The parent() command does not accept a selector argument

B. The children() command cannot filter by class

C. The parent() command returns all ancestors, not immediate parent

D. The children() command returns siblings, not children

Solution

1. Step 1: Check parent() usage

   The parent() command in Cypress does not accept any selector argument; it always returns the immediate parent element.

2. Step 2: Verify other commands

   children() can filter by selector, so that part is valid. parent() does not return all ancestors, only immediate parent. children() returns direct children, not siblings.

3. Final Answer:

   The parent() command does not accept a selector argument -> Option A

4. Quick Check:

   parent() takes no selector argument [OK]

Hint: parent() never takes a selector; children() can filter [OK]

Common Mistakes:

• Passing selector to parent()
• Confusing children() filtering
• Thinking parent() returns all ancestors

5. Given this HTML:

<ul class='menu'>
  <li class='item'>Home</li>
  <li class='item'>About</li>
  <li class='item'>Contact</li>
</ul>
<div class='footer'>Footer content</div>

Which Cypress command chain correctly selects the <ul> element starting from the <li> elements with class item?

hard

A. cy.get('.item').children('ul')

B. cy.get('.item').parent().parent()

C. cy.get('.item').children()

D. cy.get('.item').parent()

Solution

1. Step 1: Identify the parent of .item elements

   Each <li class='item'> is a direct child of the <ul class='menu'> element.

2. Step 2: Use parent() to get immediate parent

   cy.get('.item').parent() correctly gets the immediate parent <ul class='menu'> element.

3. Step 3: Check other options

   children('ul') is wrong because <li> elements do not have <ul> children. parent().parent() goes too far up. children() gets children, not parent.

4. Final Answer:

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

5. Quick Check:

   parent() gets immediate parent [OK]

Hint: Use parent() to get immediate parent element [OK]

Common Mistakes:

• Using children() to get parent
• Going two levels up unnecessarily
• Assuming children() returns parent