cy.get() with CSS selectors in Cypress - Framework Patterns

Framework Mode - cy.get() with CSS selectors

Folder Structure for Cypress Test Framework

    cypress/
    ├── e2e/                  # Test files using cy.get() with CSS selectors
    │   ├── login.cy.js       # Example test file
    │   └── dashboard.cy.js
    ├── fixtures/             # Test data files (JSON)
    │   └── users.json
    ├── support/              # Support files and custom commands
    │   ├── commands.js       # Custom cy.get() wrappers or helpers
    │   └── e2e.js            # Global setup for tests
    └── videos/               # Test run videos (auto-generated)

    cypress.config.js          # Cypress configuration file
    package.json               # Project dependencies and scripts
    

Test Framework Layers

• Test Layer: Files in cypress/e2e/ contain tests that use cy.get() with CSS selectors to find elements on the page.
• Support Layer: cypress/support/commands.js can hold custom commands that wrap cy.get() for reusable selectors.
• Fixtures Layer: Static test data in cypress/fixtures/ to separate data from test code.
• Configuration Layer: cypress.config.js manages environment settings, base URLs, and browser options.

Configuration Patterns

Use cypress.config.js to define:

• Base URL: Set baseUrl for easy cy.visit() calls.
• Environment Variables: Use env to store credentials or flags, accessed via Cypress.env().
• Browser Selection: Run tests in different browsers via CLI or config.
• Custom Command Setup: Add reusable cy.get() selectors in commands.js for maintainability.

    // cypress.config.js example
    import { defineConfig } from 'cypress'

    export default defineConfig({
      e2e: {
        baseUrl: 'https://example.com',
        env: {
          username: 'testuser',
          password: 'testpass'
        },
        setupNodeEvents(on, config) {
          // implement node event listeners here
        }
      }
    })
    

Test Reporting and CI/CD Integration

• Use built-in Cypress Dashboard or third-party reporters (like Mochawesome) for detailed test reports.
• Configure package.json scripts to run tests headlessly in CI environments.
• Integrate with CI/CD pipelines (GitHub Actions, Jenkins, GitLab CI) to run tests on code push or pull requests.
• Save screenshots and videos on test failures for easier debugging.

Best Practices for Using cy.get() with CSS Selectors

1. Use Data Attributes: Prefer selectors like [data-cy='submit-button'] instead of classes or IDs that may change.
2. Keep Selectors Simple: Avoid overly complex CSS selectors to reduce flakiness.
3. Use Custom Commands: Wrap common selectors in commands.js for reuse and easier maintenance.
4. Wait for Elements: Use Cypress automatic retries but add explicit waits if needed for dynamic content.
5. Organize Tests: Group tests logically in cypress/e2e/ and keep selectors consistent.

Self Check Question

Where in this folder structure would you add a new custom command that wraps cy.get() for a login button selector?

Key Result

Organize Cypress tests with clear folder layers, use data attribute selectors in cy.get(), and configure environments for reliable, maintainable automation.

Practice

1. What does cy.get() do in Cypress testing?

easy

A. Starts the Cypress test runner

B. Clicks on a button automatically

C. Runs JavaScript code inside the browser

D. Finds elements on the page using CSS selectors

Solution

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

   cy.get() is used to locate elements on the web page by using CSS selectors.

2. Step 2: Differentiate from other Cypress commands

   Other commands like clicking or running code are separate; cy.get() only finds elements.

3. Final Answer:

   Finds elements on the page using CSS selectors -> Option D

4. Quick Check:

   cy.get() = Finds elements [OK]

Hint: Remember: cy.get() locates elements by CSS selectors [OK]

Common Mistakes:

• Thinking cy.get() clicks elements
• Confusing cy.get() with running scripts
• Assuming cy.get() starts tests

2. Which of the following is the correct syntax to select an element with class btn-primary using cy.get()?

easy

A. cy.get('#btn-primary')

B. cy.get('btn-primary')

C. cy.get('.btn-primary')

D. cy.get('button .btn-primary')

Solution

1. Step 1: Understand CSS selector for class

   In CSS, a class selector uses a dot before the class name, so .btn-primary selects elements with that class.

2. Step 2: Check each option

   cy.get('#btn-primary') uses an ID selector (#), which is wrong here. cy.get('btn-primary') misses the dot, so it looks for a tag named 'btn-primary'. cy.get('button .btn-primary') incorrectly uses a descendant selector (space after button), selecting buttons containing .btn-primary elements.

3. Final Answer:

   cy.get('.btn-primary') -> Option C

4. Quick Check:

   Class selector = .classname [OK]

Hint: Use dot (.) before class names in CSS selectors [OK]

Common Mistakes:

• Using # instead of . for classes
• Omitting the dot before class name
• Confusing tag selectors with class selectors

3. Given the HTML snippet:

<ul>
  <li class='item'>Apple</li>
  <li class='item'>Banana</li>
  <li class='item'>Cherry</li>
</ul>

What will cy.get('.item').should('have.length', 3) check?

medium

A. That there are exactly 3 elements with class 'item'

B. That the first element with class 'item' contains '3'

C. That the list has 3 child elements regardless of class

D. That the page has 3 lists

Solution

1. Step 1: Understand cy.get('.item')

   This selects all elements with the class 'item', which are the three <li> elements.

2. Step 2: Understand .should('have.length', 3)

   This asserts that the number of selected elements is exactly 3.

3. Final Answer:

   That there are exactly 3 elements with class 'item' -> Option A

4. Quick Check:

   cy.get('.item').length = 3 [OK]

Hint: '.should(have.length, n)' checks number of matched elements [OK]

Common Mistakes:

• Thinking it checks content inside elements
• Confusing child count with class count
• Assuming it checks number of lists

4. You wrote cy.get('button#submit').click() but the test fails with "Cannot find element" error. What is the most likely cause?

medium

A. The button does not have an ID 'submit'

B. The selector should be cy.get('#submit button')

C. You must use cy.find() instead of cy.get()

D. The click() command is not supported on buttons

Solution

1. Step 1: Analyze the selector button#submit

   This selector looks for a <button> element with ID 'submit'. If the button does not have this ID, it won't be found.

2. Step 2: Check other options

   The selector should be cy.get('#submit button') reverses the selector incorrectly. You must use cy.find() instead of cy.get() is wrong because cy.get() is correct for global selection. The click() command is not supported on buttons is false; click() works on buttons.

3. Final Answer:

   The button does not have an ID 'submit' -> Option A

4. Quick Check:

   Selector must match element attributes [OK]

Hint: Verify element attributes match your selector exactly [OK]

Common Mistakes:

• Using wrong selector syntax
• Assuming click() doesn't work on buttons
• Confusing cy.get() with cy.find()

5. You want to select the second <li> element inside a <ul id='menu'>. Which cy.get() selector is correct?

hard

A. cy.get('ul#menu li[2]')

B. cy.get('#menu li:nth-child(2)')

C. cy.get('#menu li:eq(2)')

D. cy.get('ul#menu > li:nth-type(2)')

Solution

1. Step 1: Understand CSS nth-child selector

   li:nth-child(2) selects the second child <li> element inside its parent.

2. Step 2: Evaluate each option

   cy.get('ul#menu li[2]') uses invalid attribute selector. cy.get('#menu li:eq(2)') uses jQuery syntax not supported in CSS selectors. cy.get('ul#menu > li:nth-type(2)') uses invalid 'nth-type(2)' selector.

3. Final Answer:

   cy.get('#menu li:nth-child(2)') -> Option B

4. Quick Check:

   Use nth-child(n) to select nth element [OK]

Hint: Use :nth-child(n) to pick the nth child element [OK]

Common Mistakes:

• Using jQuery :eq() in CSS selectors
• Using attribute selectors incorrectly
• Confusing nth-child with nth-of-type