Cypress vs Selenium vs Playwright comparison - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Key difference in architecture between Cypress and Selenium

Which statement best describes the architectural difference between Cypress and Selenium?

A Cypress and Selenium both run inside the browser but use different scripting languages.

B Selenium runs inside the browser and controls it directly, while Cypress operates outside the browser using WebDriver protocol.

C Both Cypress and Selenium run outside the browser but use different protocols to communicate.

D Cypress runs inside the browser and controls it directly, while Selenium operates outside the browser using WebDriver protocol.

💡 Hint

Think about where the test code executes relative to the browser.

Cypress runs its test code inside the browser, giving it direct access to DOM and network, while Selenium uses WebDriver to communicate externally.

❓ Predict Output

intermediate

Output of a Playwright test snippet

What will be the output of this Playwright test code snippet when run?

Cypress

import { test, expect } from '@playwright/test';

test('check page title', async ({ page }) => {
  await page.goto('https://example.com');
  const title = await page.title();
  console.log(title);
  expect(title).toBe('Example Domain');
});

A Logs 'Example Domain' and test passes

B Logs 'Example Domain' but test fails due to wrong assertion

C Throws an error because page.title() is not a function

D Test times out because page.goto() never resolves

💡 Hint

Check the official example.com title and Playwright API usage.

The code navigates to example.com, retrieves the page title correctly, logs it, and asserts it matches 'Example Domain'.

❓ assertion

advanced

Correct assertion syntax in Cypress for element visibility

Which Cypress assertion correctly verifies that a button with id 'submit-btn' is visible on the page?

Cypress

cy.get('#submit-btn')

A cy.get('#submit-btn').should('be.visible');

B cy.get('#submit-btn').assert('visible');

C cy.get('#submit-btn').expect('visible');

D cy.get('#submit-btn').check('visible');

💡 Hint

Remember the Cypress chaining syntax for assertions.

Cypress uses the should command to assert conditions like visibility.

🔧 Debug

advanced

Identify the cause of flaky test in Selenium

A Selenium test intermittently fails with a 'NoSuchElementException' when trying to click a button. Which is the most likely cause?

A The button's locator is incorrect and never matches any element.

B The browser driver is outdated and incompatible with the browser version.

C The test tries to click the button before it is present or visible on the page.

D The test script has a syntax error causing it to stop early.

💡 Hint

Consider timing issues and element readiness in UI tests.

Flaky failures often happen when tests interact with elements before they are loaded or visible. Waiting or explicit waits help.

❓ framework

expert

Choosing the best framework for cross-browser testing with modern features

You need a testing framework that supports modern JavaScript features, runs tests in multiple browsers including Chromium, Firefox, and WebKit, and provides automatic waiting and network interception. Which framework best fits these requirements?

A Cypress

B Playwright

C Selenium WebDriver

D Jest

💡 Hint

Consider browser support and built-in features for modern web apps.

Playwright supports Chromium, Firefox, and WebKit with automatic waiting and network interception, making it ideal for modern cross-browser testing.