cypress-real-events for native events - Build an Automation Script

Verify native click and typing using cypress-real-events

Preconditions (2)

Step 1: Open the web page at 'http://localhost:3000/testpage'

Step 2: Use native click event to click the button with id 'submit-btn'

Step 3: Use native typing event to type 'Hello123' into the input field with id 'name-input'

Step 4: Verify that the button click triggers a visible alert with text 'Button clicked!'

Step 5: Verify that the input field contains the typed text 'Hello123'

✅ Expected Result: The button is clicked using a native event, triggering the alert. The input field receives the typed text using native typing events.

Automation Requirements - Cypress with cypress-real-events plugin

Assertions Needed:

Alert with text 'Button clicked!' is shown after button click

Input field with id 'name-input' contains text 'Hello123'

Best Practices:

Use cy.realClick() and cy.realType() from cypress-real-events for native events

Avoid using cy.click() and cy.type() for this test to demonstrate native event behavior

Use explicit assertions with cy.on('window:alert') to verify alert text

Use clear and stable selectors (id selectors) for elements

Automated Solution

Cypress

import 'cypress-real-events/support';

describe('Native events test with cypress-real-events', () => {
  beforeEach(() => {
    cy.visit('http://localhost:3000/testpage');
  });

  it('should click button and type text using native events', () => {
    // Listen for alert and verify text
    cy.on('window:alert', (text) => {
      expect(text).to.equal('Button clicked!');
    });

    // Use native click event
    cy.get('#submit-btn').realClick();

    // Use native typing event
    cy.get('#name-input').realClick().realType('Hello123');

    // Verify input value
    cy.get('#name-input').should('have.value', 'Hello123');
  });
});

The test imports the cypress-real-events support to enable native event commands.

In beforeEach, it visits the test page URL.

The test listens for the window:alert event to assert the alert text triggered by the button click.

It uses cy.realClick() to perform a native click on the button with id submit-btn.

Then it uses cy.realClick() followed by cy.realType() to type Hello123 into the input field with id name-input.

Finally, it asserts that the input field's value matches the typed text.

This approach ensures the test uses real browser events, which can catch issues that synthetic Cypress events might miss.

Common Mistakes - 3 Pitfalls

Using cy.click() and cy.type() instead of cy.realClick() and cy.realType()

{'mistake': 'Not listening for window:alert event to verify alert text', 'why_bad': 'Without listening, the alert may block the test or the assertion will be missed.', 'correct_approach': "Use cy.on('window:alert', callback) to capture and assert alert text."}

Using unstable or complex selectors instead of simple id selectors

Bonus Challenge

Now add data-driven testing with 3 different input texts to type into the input field

Show Hint

Practice

1. What is the main purpose of using cypress-real-events in Cypress tests?

easy

A. To generate random test data automatically

B. To speed up test execution by skipping events

C. To simulate real native browser events like clicks and typing

D. To replace Cypress commands with custom assertions

Solution

1. Step 1: Understand the role of native events in UI testing

   Native events like clicks and typing trigger real browser behaviors that Cypress commands sometimes do not fully simulate.

2. Step 2: Identify what cypress-real-events provides

   This plugin sends real native events to elements, improving test accuracy and reliability.

3. Final Answer:

   To simulate real native browser events like clicks and typing -> Option C

4. Quick Check:

   Native event simulation = C [OK]

Hint: Remember: real-events means real user-like browser events [OK]

Common Mistakes:

• Thinking it speeds up tests by skipping events
• Confusing it with data generation tools
• Assuming it replaces assertions

2. Which of the following is the correct syntax to import and use realClick from cypress-real-events in a test?

easy

A. import { realClick } from 'cypress-real-events'; cy.get('button').realClick();

B. import realClick from 'cypress-real-events'; cy.realClick('button');

C. require('cypress-real-events').realClick('button');

D. cy.get('button').clickReal();

Solution

1. Step 1: Check the correct import style for ES modules

   The plugin exports named functions, so use import { realClick } from 'cypress-real-events'.

2. Step 2: Use the function on a Cypress element

   Call realClick() on the element returned by cy.get().

3. Final Answer:

   import { realClick } from 'cypress-real-events'; cy.get('button').realClick(); -> Option A

4. Quick Check:

   Named import + method on element = B [OK]

Hint: Use named imports and call on element chain [OK]

Common Mistakes:

• Using default import instead of named import
• Calling realClick directly on cy object
• Using require syntax in ES module context

3. Given the code below, what will be the result of the test?

cy.get('#input').realType('Hello');
cy.get('#input').should('have.value', 'Hello');

medium

A. The test passes because realType types the text correctly

B. The test fails because realType does not change input value

C. The test throws a syntax error due to wrong method name

D. The test passes but input value is empty

Solution

1. Step 1: Understand what realType does

   realType sends native keyboard events to type text into input fields, updating their value.

2. Step 2: Check the assertion

   The assertion checks if the input's value matches the typed text, which should be true after realType.

3. Final Answer:

   The test passes because realType types the text correctly -> Option A

4. Quick Check:

   realType updates input value = D [OK]

Hint: realType simulates typing, so input value updates [OK]

Common Mistakes:

• Assuming realType does not affect input value
• Confusing realType with click methods
• Expecting syntax errors from correct method

4. You wrote this test but it fails:

cy.get('#submit').realClick();

What is the most likely reason for failure?

medium

A. The selector '#submit' is invalid syntax

B. realClick is not a valid method in cypress-real-events

C. You forgot to import Cypress

D. The element is not visible or not interactable

Solution

1. Step 1: Check if element is visible and interactable

   realClick requires the element to be visible and enabled to send native click events.

2. Step 2: Verify method and selector correctness

   realClick is valid and selector syntax is correct, so these are unlikely causes.

3. Final Answer:

   The element is not visible or not interactable -> Option D

4. Quick Check:

   Element visibility needed for realClick = A [OK]

Hint: Check element visibility before realClick [OK]

Common Mistakes:

• Assuming realClick method does not exist
• Blaming selector syntax without checking visibility
• Forgetting to import cypress-real-events functions

5. You want to test a hover tooltip that only appears on a real mouse hover event. Which cypress-real-events method should you use to trigger this tooltip reliably?

hard

A. realClick()

B. realHover()

C. realType()

D. realFocus()

Solution

1. Step 1: Identify the event that triggers the tooltip

   Tooltips often appear on mouse hover events, which require a real mouseover or hover event.

2. Step 2: Match the correct cypress-real-events method

   realHover() sends native mouse hover events, triggering tooltips reliably.

3. Final Answer:

   realHover() -> Option B

4. Quick Check:

   Hover event needs realHover() = A [OK]

Hint: Use realHover() to simulate mouse hover events [OK]

Common Mistakes:

• Using realClick() instead of realHover() for hover effects
• Trying realType() which types text, not hover
• Using realFocus() which focuses but doesn't hover