What if you could click exactly the right button every time without hunting through messy code?
Why Child commands in Cypress? - Purpose & Use Cases
Imagine you want to test a web page where you need to find a list, then click a button inside one of its items. Doing this manually means writing separate steps to find the list, then find the item, then find the button inside it.
This manual way is slow and confusing. You might lose track of which element you are working on, or accidentally click the wrong button. It's easy to make mistakes and hard to keep your test code clean and clear.
Child commands let you chain commands to focus on elements inside others. You can find a parent element, then directly find and act on its child elements in one smooth step. This keeps your test code simple, clear, and less error-prone.
cy.get('.list') cy.get('.list-item').eq(0) cy.get('.button').click()
cy.get('.list').find('.list-item').eq(0).find('.button').click()
Child commands make your tests faster to write and easier to understand by clearly showing the relationship between elements.
Testing a shopping cart where you select a product from a list and click its "Add to Cart" button without accidentally clicking buttons from other products.
Manual element selection can be confusing and error-prone.
Child commands let you chain element searches inside parents smoothly.
This makes tests clearer, faster, and less likely to fail by mistake.
Practice
.find() command do in Cypress testing?Solution
Step 1: Understand the purpose of
The.find().find()command is used to search for elements inside another element, meaning it looks for child elements.Step 2: Compare with other commands
Commands like.click(),.type(), and.wait()perform actions or wait, but do not locate child elements.Final Answer:
It locates child elements inside a parent element. -> Option DQuick Check:
.find()locates children = B [OK]
- Confusing .find() with .click() or .type()
- Thinking .find() waits for elements
- Using .find() without a parent element
button inside a div with class container using Cypress?Solution
Step 1: Understand chaining commands in Cypress
First,cy.get()selects the parent element. Then,.find()locates child elements inside it.Step 2: Analyze each option
cy.get('.container').find('button') correctly usescy.get('.container')to select the parent, then.find('button')to find the child button. Other options misuse the order or commands.Final Answer:
cy.get('.container').find('button') -> Option AQuick Check:
Parent first with get(), then child with find() = A [OK]
- Swapping .get() and .find() order
- Using .find() without cy.get() first
- Selecting child before parent
cy.get('ul.menu').find('li.active').should('have.length', 2)Solution
Step 1: Understand the selector chain
cy.get('ul.menu')selects theulelement with classmenu. Then.find('li.active')findslichildren with classactive.Step 2: Understand the assertion
.should('have.length', 2)asserts that exactly 2 suchli.activeelements exist inside theul.menu.Final Answer:
It selects alllielements insideul.menuwith classactiveand checks there are 2. -> Option AQuick Check:
Find children with class and check count = A [OK]
- Confusing parent and child selectors
- Thinking it clicks or types instead of asserting
- Misreading the assertion purpose
cy.find('.list').get('li').should('have.length', 3)Solution
Step 1: Check command order
cy.find()is not a valid starting command.cy.get()must be used first to select the parent element.Step 2: Correct usage
The correct order iscy.get('.list').find('li')to findlichildren inside the element with classlist.Final Answer:
The order of commands is incorrect; .get() should come before .find(). -> Option CQuick Check:
Use cy.get() first, then .find() = D [OK]
- Starting with .find() instead of cy.get()
- Assuming .find() works alone
- Ignoring command chaining rules
form with id login contains exactly 3 input fields that are visible. Which Cypress code correctly uses child commands to do this?Solution
Step 1: Select the parent form element
Usecy.get('#login')to select the form with id 'login'.Step 2: Find visible input children and assert count
Use.find('input:visible')to get visible input fields inside the form, then assert there are exactly 3 with.should('have.length', 3).Final Answer:
cy.get('#login').find('input:visible').should('have.length', 3) -> Option BQuick Check:
Parent get(), then find visible inputs, then check length = C [OK]
- Using .find() before cy.get()
- Checking visibility after length assertion
- Incorrect selector order
Ready to prove it?
Pass the test and this pattern moves unknown
