cypress-real-events for native events - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Cypress test using cypress-real-events?

Consider this Cypress test code snippet that uses cypress-real-events to simulate a native click event on a button. What will be the value of clicked after the test runs?

Cypress

let clicked = false;

cy.document().then(doc => {
  const button = doc.createElement('button');
  button.textContent = 'Click me';
  button.addEventListener('click', () => { clicked = true; });
  doc.body.appendChild(button);
  cy.get('button').realClick();
}).then(() => {
  cy.wrap(null).then(() => {
    // Check clicked value here
  });
});

A clicked remains false because realClick does not trigger native events

B Test throws an error because realClick is not a valid Cypress command

C clicked is undefined because the variable is out of scope

D clicked becomes true because realClick triggers the native click event

💡 Hint

Remember that cypress-real-events triggers native browser events, unlike Cypress's default .click()

The realClick() command from cypress-real-events triggers the native click event on the button element. This causes the event listener to run and sets clicked to true.

❓ assertion

intermediate

Which assertion correctly verifies a native keyboard event triggered by cypress-real-events?

You want to test that pressing the 'Enter' key on an input triggers a native keydown event that sets pressedEnter to true. Which assertion correctly verifies this after using realPress('Enter')?

Cypress

let pressedEnter = false;

cy.get('input').then($input => {
  $input[0].addEventListener('keydown', e => {
    if (e.key === 'Enter') pressedEnter = true;
  });
  cy.wrap($input).realPress('Enter');
});

A cy.wrap(null).should(() => { expect(pressedEnter).to.be.true; });

B cy.get('input').should('have.value', 'Enter').and(() => { expect(pressedEnter).to.be.true; });

C cy.wrap(null).should(() => { expect(pressedEnter).to.equal('Enter'); });

D cy.get('input').should('have.focus').and(() => { expect(pressedEnter).to.be.false; });

💡 Hint

The variable is outside the DOM, so use cy.wrap(null) to assert its value.

Since pressedEnter is a variable outside the DOM, the assertion must be wrapped in cy.wrap(null).should() to wait and check its value. Option A correctly asserts it is true.

🔧 Debug

advanced

Why does this cypress-real-events test fail to trigger a native mouseover event?

This test tries to trigger a native mouseover event on a div but the event listener never runs. What is the most likely reason?

Cypress

let hovered = false;

cy.get('div#hover-target').realHover().then($div => {
  $div[0].addEventListener('mouseover', () => { hovered = true; });
});

A The event listener is added after the realHover command runs, so it misses the event

B hovered variable is not accessible inside the event listener

C The selector 'div#hover-target' is invalid and does not find the element

D realHover does not trigger native mouseover events, only mouseenter

💡 Hint

Check the order of commands and event listener attachment.

The event listener is added inside the then callback, but realHover() is called outside that callback, so it runs before the listener is attached. The event is missed.

❓ framework

advanced

Which cypress-real-events command simulates a native drag and drop sequence?

You want to simulate a native drag and drop on an element using cypress-real-events. Which command sequence correctly triggers native drag events?

A cy.get('#drag').trigger('dragstart').trigger('drag').trigger('drop');

B cy.get('#drag').realMouseDown().realMouseMove(100, 0).realMouseUp();

C cy.get('#drag').realDrag();

D cy.get('#drag').realClick().realClick();

💡 Hint

Native drag and drop requires mouse down, move, then mouse up events.

Option B uses realMouseDown(), realMouseMove(), and realMouseUp() to simulate the native drag sequence. Other options either use synthetic events or invalid commands.

🧠 Conceptual

expert

Why is using cypress-real-events preferred over Cypress's default .click() for testing native event handlers?

Select the best explanation for why cypress-real-events commands like realClick() are preferred when testing native event handlers in web applications.

A Because cypress-real-events automatically retries commands on failure, unlike Cypress's default commands.

B Because Cypress's default .click() triggers native events but does not wait for animations, causing flaky tests.

C Because cypress-real-events triggers native browser events that bubble and behave exactly like real user interactions, ensuring event listeners relying on native events run correctly.

D Because Cypress's default .click() only works on buttons, while cypress-real-events works on all elements.

💡 Hint

Think about how native events differ from synthetic events in browser behavior.

Cypress's default .click() triggers synthetic events that may not behave exactly like native browser events. cypress-real-events triggers real native events, ensuring event listeners that depend on native event properties and bubbling behave correctly.

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