Why Cypress is built for modern web testing - Automation Benefits in Action

Verify Cypress can test a modern web application login flow

Preconditions (2)

Step 1: Open the web application homepage

Step 2: Locate the username input field and enter 'testuser'

Step 3: Locate the password input field and enter 'Test@1234'

Step 4: Click the login button

Step 5: Wait for the dashboard page to load

Step 6: Verify the URL contains '/dashboard'

Step 7: Verify the dashboard page shows a welcome message containing 'Welcome, testuser'

✅ Expected Result: User is successfully logged in and redirected to the dashboard page with a welcome message

Automation Requirements - Cypress

Assertions Needed:

Verify URL contains '/dashboard' after login

Verify welcome message contains username 'testuser'

Best Practices:

Use cy.get() with data-cy attributes for selectors

Use cy.contains() for text verification

Use explicit waits with cy.intercept() or cy.wait() for network calls

Keep tests isolated and independent

Use beforeEach() to set up preconditions

Automated Solution

Cypress

describe('Modern Web App Login Flow', () => {
  beforeEach(() => {
    cy.visit('http://localhost:3000')
  })

  it('logs in successfully and shows dashboard', () => {
    cy.get('[data-cy=username-input]').type('testuser')
    cy.get('[data-cy=password-input]').type('Test@1234')
    cy.get('[data-cy=login-button]').click()

    // Wait for dashboard to load by checking URL
    cy.url().should('include', '/dashboard')

    // Verify welcome message
    cy.contains('Welcome, testuser').should('be.visible')
  })
})

This Cypress test suite automates the login flow of a modern web application.

beforeEach() ensures the homepage is loaded before each test.

Selectors use data-cy attributes for stable and clear targeting.

We type the username and password, then click the login button.

We assert the URL contains /dashboard to confirm navigation.

Finally, we check the welcome message is visible and contains the username.

This approach uses Cypress best practices like explicit assertions and clear selectors.

Common Mistakes - 3 Pitfalls

Using CSS classes or IDs that frequently change as selectors

Not waiting for page or network to load before assertions

Mixing multiple test steps in one test without clear separation

Bonus Challenge

Now add data-driven testing to run the login test with 3 different username and password combinations

Show Hint

Practice

1. What is one main reason Cypress is built specifically for modern web testing?

easy

A. It uses outdated browser automation techniques.

B. It requires manual test execution only.

C. It only supports testing on mobile devices.

D. It runs tests directly in the browser alongside the app.

Solution

1. Step 1: Understand Cypress test execution

   Cypress runs tests inside the browser where the app runs, allowing real-time interaction and faster feedback.

2. Step 2: Compare options with Cypress design

   Options A, B, and C contradict Cypress's modern approach. It supports desktop browsers, runs tests automatically, and uses modern automation.

3. Final Answer:

   It runs tests directly in the browser alongside the app. -> Option D

4. Quick Check:

   Runs tests in browser = D [OK]

Hint: Remember Cypress runs tests inside the browser itself [OK]

Common Mistakes:

• Thinking Cypress only works on mobile
• Believing tests run outside the browser
• Assuming manual test runs only

2. Which of the following is the correct way to start a Cypress test block?

easy

A. test('My test', () => { ... })

B. describe('My test', () => { ... })

C. it('My test', () => { ... })

D. run('My test', () => { ... })

Solution

1. Step 1: Recall Cypress test syntax

   Cypress uses it() to define individual test cases inside describe() blocks.

2. Step 2: Identify correct test block starter

   it() is the function to start a test case. describe() groups tests, but does not start a test itself.

3. Final Answer:

   it('My test', () => { ... }) -> Option C

4. Quick Check:

   Test case starts with it() = A [OK]

Hint: Tests start with it(), groups with describe() [OK]

Common Mistakes:

• Using test() which is not Cypress syntax
• Confusing describe() as test starter
• Using run() which does not exist

3. Given the code:

cy.visit('https://example.com')
cy.get('button').click()
cy.url().should('include', '/dashboard')

What will this test check?

medium

A. That clicking the button navigates to a URL containing '/dashboard'

B. That the button is visible on the page

C. That the page title contains 'dashboard'

D. That the button is disabled

Solution

1. Step 1: Analyze each Cypress command

   cy.visit() opens the page, cy.get('button').click() clicks the button, and cy.url().should('include', '/dashboard') asserts the URL includes '/dashboard'.

2. Step 2: Understand the assertion

   The assertion checks if after clicking the button, the URL changes to include '/dashboard', indicating navigation.

3. Final Answer:

   That clicking the button navigates to a URL containing '/dashboard' -> Option A

4. Quick Check:

   URL includes '/dashboard' after click = B [OK]

Hint: Look at the assertion on cy.url() for navigation check [OK]

Common Mistakes:

• Thinking it checks button visibility
• Confusing URL check with page title
• Assuming button is disabled

4. Identify the error in this Cypress test code:

describe('Login test', () => {
  it('logs in user', () => {
    cy.visit('https://app.com')
    cy.get('#username').type('user1')
    cy.get('#password').type('pass123')
    cy.get('button.submit').click
    cy.url().should('include', '/home')
  })
})

medium

A. Wrong selector for username input

B. Missing parentheses after click method

C. cy.visit URL is incorrect

D. Missing assertion after typing password

Solution

1. Step 1: Check method calls in the code

   The line cy.get('button.submit').click misses parentheses, so the click method is not called.

2. Step 2: Verify other parts

   Selectors and URL look valid, and assertion after typing password is not required. The main error is missing parentheses on click.

3. Final Answer:

   Missing parentheses after click method -> Option B

4. Quick Check:

   Method calls need () = A [OK]

Hint: Check all method calls have () after them [OK]

Common Mistakes:

• Ignoring missing parentheses on click
• Assuming selector is wrong without checking
• Thinking cy.visit URL is invalid

5. Why does Cypress provide real-time test results and automatic waiting, making it ideal for modern web apps?

hard

A. Because it controls the browser and app in the same run loop

B. Because it requires explicit waits for every action

C. Because it runs outside the browser and uses manual waits

D. Because it only supports static HTML pages

Solution

1. Step 1: Understand Cypress architecture

   Cypress runs inside the browser and shares the same run loop as the app, allowing it to control and observe app behavior closely.

2. Step 2: Explain real-time results and automatic waits

   This architecture lets Cypress automatically wait for elements and commands, and show test results live without manual delays.

3. Final Answer:

   Because it controls the browser and app in the same run loop -> Option A

4. Quick Check:

   Same run loop control = C [OK]

Hint: Same run loop means automatic waits and live results [OK]

Common Mistakes:

• Thinking Cypress runs outside browser
• Assuming manual waits are needed
• Believing it only supports static pages