Bird
Raised Fist0
Cypresstesting~8 mins

cy.find() within parent in Cypress - Framework Patterns

Choose your learning style10 modes available
Framework Mode - .find() within parent
Folder Structure
  cypress/
  ├── e2e/                  # Test files
  │   ├── login.cy.js       # Example test
  │   └── userProfile.cy.js
  ├── fixtures/             # Test data files (JSON)
  │   └── users.json
  ├── support/              # Custom commands and utilities
  │   ├── commands.js       # Custom Cypress commands
  │   └── e2e.js            # Global support file
  └── pages/                # Page Object files
      └── loginPage.js      # Login page selectors and actions
  cypress.config.js          # Cypress configuration file
  
Test Framework Layers
  • Test Layer (cypress/e2e): Contains test scripts that use .find() within parent elements to locate nested elements reliably.
  • Page Object Layer (cypress/pages): Encapsulates selectors and actions. Uses cy.get() and .find() to locate elements inside parent containers for better maintainability.
  • Support Layer (cypress/support): Holds custom commands and reusable utilities to extend Cypress capabilities, e.g., custom commands wrapping .find().
  • Fixtures Layer (cypress/fixtures): Stores test data in JSON files to support data-driven testing.
  • Configuration Layer (cypress.config.js): Defines environment variables, base URLs, and browser settings.
Configuration Patterns
  • Environment Variables: Use cypress.env.json or cypress.config.js to store URLs, credentials, and environment-specific data.
  • Browser Settings: Configure browsers in cypress.config.js to run tests in Chrome, Firefox, or Edge.
  • Base URL: Set baseUrl in config for easy navigation with cy.visit().
  • Custom Commands: Define commands in cypress/support/commands.js to wrap common patterns like .find() within parents for cleaner tests.
Test Reporting and CI/CD Integration
  • Test Reporting: Use built-in Cypress Dashboard or plugins like mochawesome for detailed HTML reports showing pass/fail results.
  • CI/CD Integration: Integrate Cypress tests in pipelines (GitHub Actions, Jenkins, GitLab CI) to run tests on code push or pull requests.
  • Artifacts: Save screenshots and videos on test failures for debugging.
Framework Design Principles
  • Use .find() within parent elements: This scopes element searches to a specific container, reducing flaky tests caused by duplicate selectors.
  • Page Object Model: Keep selectors and actions in page files to avoid duplication and ease maintenance.
  • Custom Commands: Wrap common .find() patterns in commands for readability and reuse.
  • Explicit Assertions: Always assert element existence or state after .find() to catch failures early.
  • Data-Driven Testing: Use fixtures to separate test data from test logic, improving clarity.
Self Check

Where in this folder structure would you add a new page object file for a "User Profile" page that uses .find() to locate nested elements?

Key Result
Use .find() within parent elements in page objects and tests to scope element searches and improve test reliability.

Practice

(1/5)
1. What is the main purpose of using cy.find() in Cypress tests?
easy
A. To replace cy.get() for all element searches
B. To find elements anywhere on the page without restriction
C. To search for child elements within a specific parent element
D. To execute JavaScript code inside the browser console

Solution

  1. Step 1: Understand cy.find() role

    cy.find() is used to look for elements inside a previously selected parent element, narrowing the search.
  2. Step 2: Compare with other commands

    cy.get() searches the whole page, while cy.find() limits to children of a parent element.
  3. Final Answer:

    To search for child elements within a specific parent element -> Option C
  4. Quick Check:

    cy.find() = child search inside parent [OK]
Hint: Remember: cy.find() searches only inside a parent element [OK]
Common Mistakes:
  • Thinking cy.find() searches the whole page
  • Confusing cy.find() with cy.get()
  • Using cy.find() without a parent element first
2. Which of the following is the correct syntax to find a button with class submit-btn inside a div with id form-container using cy.find()?
easy
A. cy.find('div#form-container').find('button.submit-btn')
B. cy.get('#form-container').find('button.submit-btn')
C. cy.get('button.submit-btn').find('#form-container')
D. cy.find('#form-container').get('button.submit-btn')

Solution

  1. Step 1: Select the parent element correctly

    Use cy.get('#form-container') to select the div with the given id.
  2. Step 2: Use find() on the parent to locate the child button

    Call .find('button.submit-btn') on the parent to get the button inside it.
  3. Final Answer:

    cy.get('#form-container').find('button.submit-btn') -> Option B
  4. Quick Check:

    Parent get + find child = cy.get('#form-container').find('button.submit-btn') [OK]
Hint: Always get parent first, then find child inside it [OK]
Common Mistakes:
  • Using cy.find() before cy.get() for parent
  • Swapping order of get and find
  • Using find on a selector string instead of a parent element
3. Given the HTML:
<div id='list'>
  <ul>
    <li class='item'>Apple</li>
    <li class='item'>Banana</li>
    <li class='item'>Cherry</li>
  </ul>
</div>

What will the following Cypress code return?
cy.get('#list').find('li.item').its('length')
medium
A. 3
B. 1
C. 0
D. Error: No elements found

Solution

  1. Step 1: Select the parent div with id 'list'

    cy.get('#list') selects the div containing the list.
  2. Step 2: Find all li elements with class 'item' inside the div

    .find('li.item') selects all three list items: Apple, Banana, Cherry.
  3. Step 3: Get the length property

    .its('length') returns the number of matched elements, which is 3.
  4. Final Answer:

    3 -> Option A
  5. Quick Check:

    3 list items found inside parent [OK]
Hint: Count matched children with .find() then .its('length') [OK]
Common Mistakes:
  • Assuming find returns only one element
  • Confusing .get() and .find() scopes
  • Expecting zero because of wrong selector
4. You wrote this Cypress code:
cy.get('.container').find('.button').click()

But the test fails with "Cannot read property 'click' of undefined". What is the likely cause?
medium
A. The selector '.button' does not exist inside '.container'
B. You should use cy.find() before cy.get()
C. You forgot to add .should('be.visible') before clicking
D. The .container selector is invalid syntax

Solution

  1. Step 1: Understand the error message

    "Cannot read property 'click' of undefined" means the element was not found, so click() fails.
  2. Step 2: Check the selectors used

    If '.button' does not exist inside '.container', then .find('.button') returns nothing, causing the error.
  3. Final Answer:

    The selector '.button' does not exist inside '.container' -> Option A
  4. Quick Check:

    Missing child element causes undefined click [OK]
Hint: Check if child selector exists inside parent before clicking [OK]
Common Mistakes:
  • Using find before get
  • Assuming visibility causes this error
  • Thinking selector syntax is wrong without checking
5. You want to test a list where each div.card contains a button.delete. How do you click the delete button only inside the second card using cy.find()?
hard
A. cy.find('div.card').eq(1).get('button.delete').click()
B. cy.get('div.card').find('button.delete').eq(1).click()
C. cy.get('button.delete').eq(1).click()
D. cy.get('div.card').eq(1).find('button.delete').click()

Solution

  1. Step 1: Select the second card div

    cy.get('div.card').eq(1) selects the second card (index 1).
  2. Step 2: Find the delete button inside that card

    .find('button.delete') searches only inside the selected card.
  3. Step 3: Click the found button

    .click() clicks the delete button inside the second card only.
  4. Final Answer:

    cy.get('div.card').eq(1).find('button.delete').click() -> Option D
  5. Quick Check:

    Get second card, then find button inside it [OK]
Hint: Select parent first with eq(), then find child inside it [OK]
Common Mistakes:
  • Using find before get
  • Selecting button globally then filtering
  • Using eq() after find instead of before
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard