Cypress Interview Questions Your Guide to Success

Cypress is a modern end-to-end testing framework designed for web applications. Stark.ai offers a curated collection of Cypress interview questions, real-world scenarios, and expert guidance to help you excel in your next technical interview.

Back

angular

apollo graphql

cypress

Fundamentals & Core Concepts 10
Commands & Interactions 10
Network Requests & API Testing 10
Test Organization & Structure 10
Debugging & Troubleshooting 10
CI/CD & Test Automation 10
Test Patterns & Best Practices 10
Performance & Optimization 10
Security Testing 10
Cross browser Testing 10
Mobile Testing 10

flutter

ionic

java

javascript

jest

laravel

mocha

nextjs

nodejs

php

python

react native

reactjs

sql

svelte

swift

typescript

vuejs

HR Questions MBA Questions Start Mock Interview

cypress

Fundamentals & Core Concepts
- What is Cypress and how does it differ from Selenium?
  
  Cypress is a modern, all-in-one testing framework for web applications that executes tests in the same run loop as...
- What are the key features of Cypress?
  
  Key features include: 1) Automatic waiting and retry-ability, 2) Real-time reloads, 3) Consistent results due to...
- What is the Cypress Test Runner?
  
  The Cypress Test Runner is an interactive interface that allows you to see commands as they execute, view the...
- How do you install and initialize Cypress in a project?
  
  Cypress can be installed using npm: 'npm install cypress --save-dev'. After installation, initialize it using 'npx...
- What is the structure of a basic Cypress test?
  
  A basic Cypress test uses describe() blocks for test suites and it() blocks for individual tests. Tests typically...
- What are Cypress commands and how do they work?
  
  Cypress commands are chainable methods that perform actions, assertions, or retrieve elements. They are asynchronous...
- How does Cypress handle asynchronous operations?
  
  Cypress automatically handles asynchronous operations through its command queue. Commands are executed sequentially,...
- What are aliases in Cypress and how are they used?
  
  Aliases are references to elements, routes, or values that can be reused throughout tests. They are created using...
- How do you handle assertions in Cypress?
  
  Cypress includes Chai assertions and extensions through .should() and .expect(). Assertions automatically retry...
- What is the difference between cy.get() and cy.find()?
  
  cy.get() searches for elements in the entire DOM and starts a new command chain. cy.find() searches for elements...
Commands & Interactions
- What are the main types of Cypress commands?
  
  Cypress commands fall into several categories: 1) Parent commands that begin a new chain (cy.get(), cy.visit()), 2)...
- How do you select elements in Cypress?
  
  Elements can be selected using cy.get() with CSS selectors, cy.contains() for text content, data-* attributes for...
- What are the common interaction commands in Cypress?
  
  Common interaction commands include: .click() for clicking elements, .type() for input fields, .select() for...
- How do you type into input fields?
  
  The .type() command is used for input fields. It supports special characters, key combinations, and delay options....
- What is the purpose of cy.wait() and when should it be used?
  
  cy.wait() is used to wait for a specific duration or for aliases/routes to resolve. It's primarily used with network...
- How do you handle dropdowns in Cypress?
  
  Dropdowns are handled using .select() command for <select> elements. You can select by value, text, or index....
- What is the difference between .click() and .trigger('click')?
  
  .click() simulates a user click with additional checks and waitings, while .trigger('click') fires the raw event...
- How do you handle checkboxes and radio buttons?
  
  Use .check() to check and .uncheck() for checkboxes. Radio buttons use .check() only. Both commands can take values...
- What is the purpose of .within() command?
  
  .within() scopes subsequent commands to elements within a specific DOM element. It's useful for limiting the context...
- How do you scroll elements into view?
  
  Cypress automatically scrolls elements into view before interactions. You can also use .scrollIntoView() explicitly...
Network Requests & API Testing
- What is cy.intercept() and how is it used?
  
  cy.intercept() is used to stub and spy on network requests. It can modify network responses, delay requests, and...
- How do you make HTTP requests in Cypress?
  
  HTTP requests can be made using cy.request() for direct API calls. It supports different HTTP methods, headers, and...
- What is the difference between cy.request() and cy.intercept()?
  
  cy.request() makes actual HTTP requests and is used for direct API testing, while cy.intercept() intercepts and...
- How do you stub network responses?
  
  Network responses can be stubbed using cy.intercept() with static data or fixtures. Example: cy.intercept('GET',...
- What are fixtures and how are they used in API testing?
  
  Fixtures are static data files used for test data and network stubs. They're stored in cypress/fixtures and loaded...
- How do you wait for network requests to complete?
  
  Use cy.wait() with aliased requests to wait for completion. Example: cy.intercept('GET',...
- How do you verify request parameters and headers?
  
  Request parameters and headers can be verified using cy.intercept() with a callback function. Example:...
- What is request aliasing and why is it useful?
  
  Request aliasing assigns names to intercepted requests using .as(). It allows waiting for specific requests and...
- How do you handle authentication in API requests?
  
  Authentication can be handled by setting headers in cy.request() or cy.intercept(), using beforeEach hooks for token...
- What are common HTTP status codes and how do you test them?
  
  Common status codes (200, 201, 400, 401, 403, 404, 500) can be tested using statusCode in cy.request() assertions or...
Test Organization & Structure
- What is the standard folder structure in a Cypress project?
  
  A standard Cypress project includes: cypress/e2e for test files, cypress/fixtures for test data, cypress/support for...
- What are test hooks in Cypress and how are they used?
  
  Cypress provides before(), beforeEach(), after(), and afterEach() hooks for test setup and cleanup. before() runs...
- How do you organize test files in Cypress?
  
  Test files are typically organized by feature, page, or functionality using .cy.js or .cy.ts extensions. Group...
- What is the purpose of cypress.config.js?
  
  cypress.config.js is the main configuration file that defines project-wide settings like baseUrl, default timeouts,...
- How do you handle global configuration in Cypress?
  
  Global configuration can be set in cypress.config.js, support/e2e.js, or through environment variables. Common...
- What is the role of support files in Cypress?
  
  Support files (in cypress/support) contain reusable code like custom commands, global configurations, and shared...
- How do you structure describe and it blocks?
  
  describe blocks group related tests and can be nested. it blocks contain individual test cases. Use descriptive...
- What are custom commands and how are they created?
  
  Custom commands are reusable functions added using Cypress.Commands.add(). They're defined in support/commands.js...
- How do you manage test data in Cypress?
  
  Test data can be managed using fixtures (JSON files in cypress/fixtures), environment variables, or custom data...
- What is the difference between before and beforeEach hooks?
  
  before runs once before all tests in a describe block, while beforeEach runs before each individual test. before is...
Debugging & Troubleshooting
- What debugging tools are available in Cypress?
  
  Cypress provides several debugging tools: 1) Debug command (.debug()), 2) Chrome DevTools integration, 3) Command...
- How do you use .debug() command in Cypress?
  
  The .debug() command pauses test execution and opens Chrome DevTools. It can be chained to any Cypress command to...
- What is the purpose of cy.log()?
  
  cy.log() adds messages to the Command Log in the Test Runner. It's useful for debugging by providing additional...
- How does Cypress handle test failures?
  
  Cypress provides detailed error messages, screenshots on failure, video recordings, and stack traces. It...
- What is time travel debugging in Cypress?
  
  Time travel debugging allows you to see the state of your application at each step of test execution. The Test...
- How do you inspect network requests in Cypress?
  
  Network requests can be inspected using the Network tab in DevTools, cy.intercept() for request monitoring, and Test...
- What are common causes of flaky tests?
  
  Common causes include: 1) Race conditions, 2) Improper waiting, 3) Network timing issues, 4) Animations, 5) State...
- How do you handle timeouts in Cypress?
  
  Timeouts can be configured globally in cypress.config.js or per-command using timeout option. Default timeouts can...
- What is the purpose of screenshots and videos in Cypress?
  
  Screenshots and videos are automatically captured on test failure (configurable). They help in debugging by...
- How do you debug synchronization issues?
  
  Synchronization issues can be debugged using proper waiting strategies, .debug() command at key points, and...
CI/CD & Test Automation
- How do you integrate Cypress with CI/CD pipelines?
  
  Cypress can be integrated with CI/CD pipelines using cypress run command, configuring environment variables, and...
- What is the difference between cypress open and cypress run?
  
  cypress open launches the Test Runner UI for interactive testing and debugging, while cypress run executes tests...
- How do you configure test reporting in CI/CD?
  
  Test reporting can be configured using built-in reporters (spec, junit, json) or custom reporters. Reports can be...
- What are environment variables in Cypress CI/CD?
  
  Environment variables control test behavior in different environments. They can be set through CI/CD platform,...
- How do you handle test artifacts in CI/CD?
  
  Test artifacts (screenshots, videos, reports) can be stored using CI/CD platform's artifact storage. Configure...
- What is parallel test execution in Cypress?
  
  Parallel test execution runs tests concurrently across multiple machines/containers to reduce execution time....
- How do you handle test retries in CI/CD?
  
  Test retries can be configured using retries option in cypress.config.js or command line. Helps handle flaky tests...
- What is the Cypress Dashboard service?
  
  Cypress Dashboard provides test recording, parallel execution, failure analysis, and team collaboration features....
- How do you manage test data in CI/CD?
  
  Test data can be managed through fixtures, database seeding, or API calls. Implement proper data cleanup, isolation...
- What is the importance of CI/CD pipeline caching?
  
  Caching npm dependencies, Cypress binary, and build artifacts reduces pipeline execution time. Configure cache paths...
Test Patterns & Best Practices
- What are the key principles of writing good Cypress tests?
  
  Key principles include: 1) Test isolation - each test should be independent, 2) Consistent selectors using data-*...
- What is the Page Object Pattern and how is it implemented in Cypress?
  
  Page Object Pattern encapsulates page elements and behaviors into classes/objects. In Cypress, it's implemented by...
- What are best practices for selector strategies in Cypress?
  
  Best practices include: 1) Using data-cy attributes for elements, 2) Avoiding brittle selectors like CSS classes or...
- How should you structure your test files?
  
  Tests should be structured with: 1) Clear describe blocks for feature groups, 2) Focused it blocks for specific...
- What is the AAA (Arrange-Act-Assert) pattern?
  
  AAA pattern structures tests into three phases: 1) Arrange - set up test data and conditions, 2) Act - perform the...
- How should you handle test data management?
  
  Test data should be: 1) Managed through fixtures or factories, 2) Isolated between tests, 3) Cleaned up after test...
- What are best practices for writing assertions?
  
  Assertion best practices include: 1) Using explicit assertions over implicit ones, 2) Writing meaningful assertion...
- How should you handle authentication in tests?
  
  Authentication should be: 1) Implemented through API calls when possible, 2) Cached between tests when appropriate,...
- What are best practices for using custom commands?
  
  Custom commands should: 1) Be reusable across tests, 2) Follow consistent naming conventions, 3) Be well-documented,...
- How should you handle waiting in tests?
  
  Waiting strategies should: 1) Use Cypress's automatic waiting when possible, 2) Avoid arbitrary timeouts, 3) Wait...
Performance & Optimization
- What factors affect Cypress test execution speed?
  
  Key factors include: 1) Number of test cases and complexity, 2) Network requests and response times, 3) Test retry...
- How can you reduce test execution time in Cypress?
  
  Test execution can be optimized by: 1) Implementing proper test parallelization, 2) Using API calls instead of UI...
- What is the role of caching in Cypress tests?
  
  Caching helps improve performance by: 1) Storing browser session data, 2) Caching network responses, 3) Maintaining...
- How do timeouts affect test performance?
  
  Timeouts impact performance through: 1) Command execution waiting times, 2) Network request timeouts, 3) Page load...
- What is the impact of screenshots and videos on test performance?
  
  Screenshots and videos affect performance by: 1) Increasing disk I/O, 2) Consuming memory resources, 3) Adding...
- How does browser instance management affect performance?
  
  Browser management impacts performance through: 1) Browser launch time, 2) Memory usage, 3) Resource allocation, 4)...
- What role does test isolation play in performance?
  
  Test isolation affects performance through: 1) State reset requirements, 2) Setup/teardown overhead, 3) Browser...
- How do network requests impact test performance?
  
  Network requests affect performance through: 1) Response waiting times, 2) Request retry overhead, 3) Payload size...
- What is the impact of logging on test performance?
  
  Logging affects performance through: 1) I/O operations, 2) Memory usage for log storage, 3) Console output...
- How do retries affect test performance?
  
  Retries impact performance through: 1) Additional test execution time, 2) Resource usage during retries, 3) State...
Security Testing
- How can you test authentication flows in Cypress?
  
  Authentication testing involves: 1) Testing login/logout flows, 2) Handling different authentication methods (OAuth,...
- What is the best practice for handling sensitive data in Cypress tests?
  
  Sensitive data handling includes: 1) Using environment variables for credentials, 2) Never committing sensitive data...
- How do you test authorization in Cypress?
  
  Authorization testing involves: 1) Verifying role-based access control, 2) Testing permission levels, 3) Checking...
- What is CSRF protection and how do you test it?
  
  CSRF testing includes: 1) Verifying CSRF token presence, 2) Testing token validation, 3) Checking token rotation, 4)...
- How can you test SSL/TLS configurations?
  
  SSL/TLS testing involves: 1) Verifying secure connection establishment, 2) Testing certificate validation, 3)...
- What are the basics of XSS testing in Cypress?
  
  XSS testing basics include: 1) Testing input validation, 2) Checking output encoding, 3) Testing script injection...
- How do you test secure cookie handling?
  
  Cookie security testing includes: 1) Verifying secure flag presence, 2) Testing HttpOnly attribute, 3) Checking...
- What is the importance of testing HTTP headers?
  
  HTTP header testing involves: 1) Verifying security headers presence, 2) Testing CORS headers, 3) Checking content...
- How do you test password policies?
  
  Password policy testing includes: 1) Testing password complexity requirements, 2) Verifying password change flows,...
- What are the basics of input validation testing?
  
  Input validation testing includes: 1) Testing boundary values, 2) Checking special character handling, 3) Testing...
Cross browser Testing
- What browsers does Cypress support for testing?
  
  Cypress supports: 1) Chrome and Chromium-based browsers (Chrome, Chromium, Edge), 2) Firefox, 3) Electron, 4) Brave....
- How do you configure different browsers in Cypress?
  
  Browser configuration involves: 1) Setting browser in cypress.config.js, 2) Using --browser flag in CLI, 3)...
- What are the common cross-browser testing challenges?
  
  Common challenges include: 1) Different rendering behaviors, 2) Feature support variations, 3) Performance...
- How do you handle browser-specific selectors?
  
  Browser-specific selectors require: 1) Using data-* attributes for consistency, 2) Implementing fallback selectors,...
- What is viewport configuration in cross-browser testing?
  
  Viewport configuration includes: 1) Setting width and height, 2) Handling responsive breakpoints, 3) Device-specific...
- How do you handle browser events across different browsers?
  
  Browser event handling includes: 1) Using browser-agnostic event triggers, 2) Implementing event polyfills when...
- What are best practices for cross-browser screenshots?
  
  Screenshot best practices include: 1) Consistent viewport settings, 2) Handling dynamic content, 3) Browser-specific...
- How do you handle browser capabilities detection?
  
  Capability detection involves: 1) Feature checking, 2) Browser version detection, 3) API support verification, 4)...
- What are common browser compatibility issues?
  
  Common issues include: 1) CSS rendering differences, 2) JavaScript API support, 3) Event handling variations, 4)...
- How do you handle browser-specific timeouts?
  
  Timeout handling includes: 1) Setting browser-specific timeout values, 2) Handling different performance...
Mobile Testing
- How does Cypress support mobile testing?
  
  Cypress supports mobile testing through: 1) Viewport configuration for mobile screen sizes, 2) Mobile event...
- How do you configure viewport for mobile testing?
  
  Mobile viewport configuration includes: 1) Using cy.viewport() command, 2) Setting specific device presets, 3)...
- What are common mobile testing challenges in Cypress?
  
  Common challenges include: 1) Touch event simulation, 2) Device-specific behavior testing, 3) Performance on mobile...
- How do you test responsive breakpoints?
  
  Breakpoint testing involves: 1) Using different viewport sizes, 2) Testing layout changes, 3) Verifying content...
- What are mobile-specific selectors?
  
  Mobile selectors include: 1) Touch-specific elements, 2) Mobile-specific classes, 3) Responsive design selectors, 4)...
- How do you handle touch events in Cypress?
  
  Touch event handling includes: 1) Using .trigger() for touch events, 2) Simulating tap actions, 3) Handling...
- What are best practices for mobile layout testing?
  
  Layout testing practices include: 1) Testing multiple viewport sizes, 2) Verifying element alignment, 3) Checking...
- How do you test mobile navigation patterns?
  
  Navigation testing includes: 1) Testing hamburger menus, 2) Verifying swipe navigation, 3) Testing bottom navigation...
- What are mobile-specific test considerations?
  
  Mobile considerations include: 1) Touch interaction testing, 2) Mobile performance testing, 3) Network condition...
- How do you test mobile-specific features?
  
  Feature testing includes: 1) Touch ID/Face ID simulation, 2) GPS location testing, 3) Camera access testing, 4)...

What is Cypress and how does it differ from Selenium?

Cypress is a modern, all-in-one testing framework for web applications that executes tests in the same run loop as the application. Unlike Selenium, which runs outside the browser and uses WebDriver for automation, Cypress runs inside the browser, providing better control, real-time reloads, and automatic waiting. It offers built-in assertions, stubbing, and spying capabilities without requiring additional tools.

What are the key features of Cypress?

Key features include: 1) Automatic waiting and retry-ability, 2) Real-time reloads, 3) Consistent results due to automatic waiting, 4) Time travel and debugging capabilities, 5) Network traffic control, 6) Screenshots and videos of test runs, 7) Cross-browser testing support, 8) Built-in assertion library, 9) Stubbing and spying on network requests, 10) Interactive test runner.

What is the Cypress Test Runner?

The Cypress Test Runner is an interactive interface that allows you to see commands as they execute, view the application under test, and inspect the DOM. It provides features like time travel, real-time reloads, and debugging tools. The Test Runner shows the command log, application preview, and detailed error messages when tests fail.

How do you install and initialize Cypress in a project?

Cypress can be installed using npm: 'npm install cypress --save-dev'. After installation, initialize it using 'npx cypress open' which creates the cypress directory with example specs and configuration. The configuration file (cypress.config.js) can be customized for project-specific settings.

What is the structure of a basic Cypress test?

A basic Cypress test uses describe() blocks for test suites and it() blocks for individual tests. Tests typically follow the pattern: visit a page, get an element, interact with it, and make assertions. Example: describe('My Test Suite', () => { it('performs an action', () => { cy.visit('/'); cy.get('button').click(); cy.contains('Result').should('be.visible'); }); });

What are Cypress commands and how do they work?

Cypress commands are chainable methods that perform actions, assertions, or retrieve elements. They are asynchronous but handle promises automatically. Commands follow a sequential order and include automatic retry-ability and waiting. Common commands include cy.visit(), cy.get(), cy.click(), cy.type(), and cy.should().

How does Cypress handle asynchronous operations?

Cypress automatically handles asynchronous operations through its command queue. Commands are executed sequentially, and Cypress automatically waits for commands to complete before moving to the next one. It includes built-in retry-ability and timeout mechanisms, eliminating the need for explicit waits or async/await syntax.

What are aliases in Cypress and how are they used?

Aliases are references to elements, routes, or values that can be reused throughout tests. They are created using cy.as() and referenced using @alias syntax. Aliases help reduce code duplication and make tests more maintainable. Example: cy.get('button').as('submitBtn') and later cy.get('@submitBtn').click().

How do you handle assertions in Cypress?

Cypress includes Chai assertions and extensions through .should() and .expect(). Assertions automatically retry until they pass or timeout. Common assertions include checking visibility, text content, element states, and DOM properties. Example: cy.get('element').should('be.visible').and('contain', 'text').

What is the difference between cy.get() and cy.find()?

cy.get() searches for elements in the entire DOM and starts a new command chain. cy.find() searches for elements within the previous subject's DOM and continues the existing chain. cy.get() is used for initial element selection, while cy.find() is used for finding nested elements.

What are the main types of Cypress commands?

Cypress commands fall into several categories: 1) Parent commands that begin a new chain (cy.get(), cy.visit()), 2) Child commands that chain from parent commands (.click(), .type()), 3) Dual commands that can start or chain (.contains()), and 4) Assertions that verify conditions (.should(), .expect()).

How do you select elements in Cypress?

Elements can be selected using cy.get() with CSS selectors, cy.contains() for text content, data-* attributes for testing, or custom selectors. Best practices include using data-cy attributes for stable selection. Chain commands like .find() and .filter() can refine selections.

What are the common interaction commands in Cypress?

Common interaction commands include: .click() for clicking elements, .type() for input fields, .select() for dropdowns, .check() and .uncheck() for checkboxes, .hover() for mouse hover, and .drag() for drag-and-drop operations.

How do you type into input fields?

The .type() command is used for input fields. It supports special characters, key combinations, and delay options. Example: cy.get('input').type('Hello World', { delay: 100 }). It can also handle special keys using {key} syntax like {enter} or {ctrl+a}.

What is the purpose of cy.wait() and when should it be used?

cy.wait() is used to wait for a specific duration or for aliases/routes to resolve. It's primarily used with network requests (cy.wait('@alias')) rather than arbitrary timeouts. For element interactions, Cypress's automatic waiting is preferred over explicit waits.

How do you handle dropdowns in Cypress?

Dropdowns are handled using .select() command for <select> elements. You can select by value, text, or index. Example: cy.get('select').select('Option 1'). For custom dropdowns, use combination of .click() and .contains() or other appropriate commands.

What is the difference between .click() and .trigger('click')?

.click() simulates a user click with additional checks and waitings, while .trigger('click') fires the raw event without extra logic. .click() is preferred for most cases as it's more reliable and closer to real user interaction.

How do you handle checkboxes and radio buttons?

Use .check() to check and .uncheck() for checkboxes. Radio buttons use .check() only. Both commands can take values for selecting specific options in groups. Example: cy.get('[type="checkbox"]').check() or cy.get('[type="radio"]').check('option1').

What is the purpose of .within() command?

.within() scopes subsequent commands to elements within a specific DOM element. It's useful for limiting the context of commands to a specific section of the page. Example: cy.get('form').within(() => { cy.get('input').type('text') }).

How do you scroll elements into view?

Cypress automatically scrolls elements into view before interactions. You can also use .scrollIntoView() explicitly or .scrollTo() for specific scroll positions. Cypress handles scrolling containers and window scrolling automatically.

What is cy.intercept() and how is it used?

cy.intercept() is used to stub and spy on network requests. It can modify network responses, delay requests, and assert on network behavior. Example: cy.intercept('GET', '/api/users', { fixture: 'users.json' }). It supports pattern matching, dynamic responses, and request/response modifications.

How do you make HTTP requests in Cypress?

HTTP requests can be made using cy.request() for direct API calls. It supports different HTTP methods, headers, and body data. Example: cy.request('POST', '/api/users', { name: 'John' }). It automatically handles cookies and follows redirects.

What is the difference between cy.request() and cy.intercept()?

cy.request() makes actual HTTP requests and is used for direct API testing, while cy.intercept() intercepts and modifies network requests made by the application. cy.request() is for testing APIs directly, while cy.intercept() is for controlling the application's network behavior.

How do you stub network responses?

Network responses can be stubbed using cy.intercept() with static data or fixtures. Example: cy.intercept('GET', '/api/data', { statusCode: 200, body: { key: 'value' } }). Stubs can include status codes, headers, and dynamic responses.

What are fixtures and how are they used in API testing?

Fixtures are static data files used for test data and network stubs. They're stored in cypress/fixtures and loaded using cy.fixture(). Example: cy.fixture('users.json').then((data) => { cy.intercept('GET', '/api/users', data) }). They help maintain consistent test data.

How do you wait for network requests to complete?

Use cy.wait() with aliased requests to wait for completion. Example: cy.intercept('GET', '/api/users').as('getUsers'); cy.wait('@getUsers'). This ensures network requests complete before continuing test execution.

How do you verify request parameters and headers?

Request parameters and headers can be verified using cy.intercept() with a callback function. Example: cy.intercept('POST', '/api/users', (req) => { expect(req.headers).to.have.property('authorization'); expect(req.body).to.have.property('name') }).

What is request aliasing and why is it useful?

Request aliasing assigns names to intercepted requests using .as(). It allows waiting for specific requests and making assertions on them. Example: cy.intercept('GET', '/api/users').as('users'). Aliases can be referenced using @ syntax.

How do you handle authentication in API requests?

Authentication can be handled by setting headers in cy.request() or cy.intercept(), using beforeEach hooks for token setup, or implementing custom commands. Consider proper token management and session handling.

What are common HTTP status codes and how do you test them?

Common status codes (200, 201, 400, 401, 403, 404, 500) can be tested using statusCode in cy.request() assertions or cy.intercept() stubs. Example: cy.request('/api/users').its('status').should('eq', 200).

What is the standard folder structure in a Cypress project?

A standard Cypress project includes: cypress/e2e for test files, cypress/fixtures for test data, cypress/support for custom commands and global configuration, cypress/downloads for downloaded files, and cypress.config.js for Cypress configuration. Integration tests go in e2e directory, while support files contain reusable code.

What are test hooks in Cypress and how are they used?

Cypress provides before(), beforeEach(), after(), and afterEach() hooks for test setup and cleanup. before() runs once before all tests, beforeEach() runs before each test, after() runs once after all tests, and afterEach() runs after each test. They help maintain test state and reduce code duplication.

How do you organize test files in Cypress?

Test files are typically organized by feature, page, or functionality using .cy.js or .cy.ts extensions. Group related tests in describe blocks, use meaningful file names, and maintain a consistent structure. Consider using subdirectories for better organization of large test suites.

What is the purpose of cypress.config.js?

cypress.config.js is the main configuration file that defines project-wide settings like baseUrl, default timeouts, viewport size, and plugin configuration. It can include environment-specific settings and custom configurations. The file is used to maintain consistent test behavior across the project.

How do you handle global configuration in Cypress?

Global configuration can be set in cypress.config.js, support/e2e.js, or through environment variables. Common configurations include baseUrl, defaultCommandTimeout, and viewportWidth/Height. Use Cypress.config() to access or modify configuration values during test execution.

What is the role of support files in Cypress?

Support files (in cypress/support) contain reusable code like custom commands, global configurations, and shared behaviors. The e2e.js file is loaded before test files and can include global setup, import custom commands, and override default behavior.

How do you structure describe and it blocks?

describe blocks group related tests and can be nested. it blocks contain individual test cases. Use descriptive names that explain the test's purpose. Example: describe('Login Feature', () => { it('should login with valid credentials', () => {...}); });

What are custom commands and how are they created?

Custom commands are reusable functions added using Cypress.Commands.add(). They're defined in support/commands.js and can be used like built-in commands. Example: Cypress.Commands.add('login', (email, password) => {...}). They help reduce code duplication and improve maintainability.

How do you manage test data in Cypress?

Test data can be managed using fixtures (JSON files in cypress/fixtures), environment variables, or custom data generation utilities. Use cy.fixture() to load data, and consider implementing data cleanup in afterEach hooks. Keep test data isolated and maintainable.

What is the difference between before and beforeEach hooks?

before runs once before all tests in a describe block, while beforeEach runs before each individual test. before is used for one-time setup like database seeding, while beforeEach is for per-test setup like resetting state or logging in.

What debugging tools are available in Cypress?

Cypress provides several debugging tools: 1) Debug command (.debug()), 2) Chrome DevTools integration, 3) Command log in Test Runner, 4) Time travel feature, 5) Screenshots and videos, 6) Console logging, and 7) Error messages with detailed stack traces.

How do you use .debug() command in Cypress?

The .debug() command pauses test execution and opens Chrome DevTools. It can be chained to any Cypress command to inspect the state at that point. Example: cy.get('button').debug().click(). This allows inspection of elements and application state.

What is the purpose of cy.log()?

cy.log() adds messages to the Command Log in the Test Runner. It's useful for debugging by providing additional context during test execution. Example: cy.log('Clicking submit button'). Messages appear in the test runner's command log.

How does Cypress handle test failures?

Cypress provides detailed error messages, screenshots on failure, video recordings, and stack traces. It automatically retries failed assertions and provides clear failure reasons in the Test Runner. Failed tests can be debugged using time travel.

What is time travel debugging in Cypress?

Time travel debugging allows you to see the state of your application at each step of test execution. The Test Runner snapshots the DOM at each command, allowing you to hover over commands and see the application state at that point.

How do you inspect network requests in Cypress?

Network requests can be inspected using the Network tab in DevTools, cy.intercept() for request monitoring, and Test Runner's command log. You can view request/response details, headers, and timing information.

What are common causes of flaky tests?

Common causes include: 1) Race conditions, 2) Improper waiting, 3) Network timing issues, 4) Animations, 5) State dependencies between tests, 6) Resource loading issues, and 7) Inconsistent test data. Understanding these helps in writing more reliable tests.

How do you handle timeouts in Cypress?

Timeouts can be configured globally in cypress.config.js or per-command using timeout option. Default timeouts can be overridden, and custom timeout messages can be provided. Example: cy.get('button', { timeout: 10000 }).

What is the purpose of screenshots and videos in Cypress?

Screenshots and videos are automatically captured on test failure (configurable). They help in debugging by providing visual evidence of test execution and failure points. Videos show the entire test run, while screenshots capture specific failure moments.

How do you debug synchronization issues?

Synchronization issues can be debugged using proper waiting strategies, .debug() command at key points, and reviewing command log timing. Understanding Cypress's automatic waiting and retry mechanism helps prevent sync issues.

How do you integrate Cypress with CI/CD pipelines?

Cypress can be integrated with CI/CD pipelines using cypress run command, configuring environment variables, and proper pipeline setup. Common integrations include GitHub Actions, Jenkins, CircleCI, and GitLab CI. Example configuration includes installing dependencies, cache management, and artifact storage.

What is the difference between cypress open and cypress run?

cypress open launches the Test Runner UI for interactive testing and debugging, while cypress run executes tests headlessly in the command line, suitable for CI/CD environments. cypress run provides additional options for CI integration like reporters and screenshot management.

How do you configure test reporting in CI/CD?

Test reporting can be configured using built-in reporters (spec, junit, json) or custom reporters. Reports can be stored as artifacts, integrated with test management tools, and used for test result analysis. Configure reporter options in cypress.config.js or command line.

What are environment variables in Cypress CI/CD?

Environment variables control test behavior in different environments. They can be set through CI/CD platform, cypress.env.json, or command line arguments. Sensitive data should be stored as secure environment variables in CI/CD platform.

How do you handle test artifacts in CI/CD?

Test artifacts (screenshots, videos, reports) can be stored using CI/CD platform's artifact storage. Configure artifact paths in pipeline configuration, implement retention policies, and manage artifact access. Use for debugging failed tests.

What is parallel test execution in Cypress?

Parallel test execution runs tests concurrently across multiple machines/containers to reduce execution time. Requires Cypress Dashboard or custom parallelization setup. Configure through CI/CD platform and proper test organization.

How do you handle test retries in CI/CD?

Test retries can be configured using retries option in cypress.config.js or command line. Helps handle flaky tests in CI/CD environment. Configure different retry strategies for run mode and open mode.

What is the Cypress Dashboard service?

Cypress Dashboard provides test recording, parallel execution, failure analysis, and team collaboration features. Integrates with CI/CD for detailed test analytics and debugging. Requires projectId and record key configuration.

How do you manage test data in CI/CD?

Test data can be managed through fixtures, database seeding, or API calls. Implement proper data cleanup, isolation between test runs, and environment-specific data handling. Consider using test data management tools.

What is the importance of CI/CD pipeline caching?

Caching npm dependencies, Cypress binary, and build artifacts reduces pipeline execution time. Configure cache paths in CI/CD configuration, implement proper cache invalidation, and monitor cache effectiveness.

What are the key principles of writing good Cypress tests?

Key principles include: 1) Test isolation - each test should be independent, 2) Consistent selectors using data-* attributes, 3) Avoiding sleep/fixed waits, 4) Proper assertion usage, 5) Following the AAA (Arrange-Act-Assert) pattern, 6) Maintaining test readability, and 7) Implementing proper error handling.

What is the Page Object Pattern and how is it implemented in Cypress?

Page Object Pattern encapsulates page elements and behaviors into classes/objects. In Cypress, it's implemented by creating classes/objects that contain selectors and methods for interacting with specific pages. This improves maintainability and reusability of test code.

What are best practices for selector strategies in Cypress?

Best practices include: 1) Using data-cy attributes for elements, 2) Avoiding brittle selectors like CSS classes or IDs that may change, 3) Following consistent naming conventions, 4) Using specific selectors over generic ones, 5) Maintaining a selector strategy guide for the team.

How should you structure your test files?

Tests should be structured with: 1) Clear describe blocks for feature groups, 2) Focused it blocks for specific behaviors, 3) Proper use of hooks for setup/cleanup, 4) Related tests grouped together, 5) Consistent file naming conventions, 6) Proper separation of concerns.

What is the AAA (Arrange-Act-Assert) pattern?

AAA pattern structures tests into three phases: 1) Arrange - set up test data and conditions, 2) Act - perform the action being tested, 3) Assert - verify the expected results. This pattern makes tests clear, maintainable, and follows a logical flow.

How should you handle test data management?

Test data should be: 1) Managed through fixtures or factories, 2) Isolated between tests, 3) Cleaned up after test execution, 4) Version controlled with tests, 5) Easily maintainable and updateable, 6) Environment-specific when needed.

What are best practices for writing assertions?

Assertion best practices include: 1) Using explicit assertions over implicit ones, 2) Writing meaningful assertion messages, 3) Testing one thing per assertion, 4) Using appropriate assertion methods, 5) Implementing proper waiting strategies before assertions.

How should you handle authentication in tests?

Authentication should be: 1) Implemented through API calls when possible, 2) Cached between tests when appropriate, 3) Properly cleaned up after tests, 4) Handled consistently across test suite, 5) Implemented with proper security considerations.

What are best practices for using custom commands?

Custom commands should: 1) Be reusable across tests, 2) Follow consistent naming conventions, 3) Be well-documented, 4) Handle errors appropriately, 5) Be maintained in a central location, 6) Follow chainable patterns when appropriate.

How should you handle waiting in tests?

Waiting strategies should: 1) Use Cypress's automatic waiting when possible, 2) Avoid arbitrary timeouts, 3) Wait for specific conditions or elements, 4) Use proper assertions for state changes, 5) Implement proper retry strategies.

What factors affect Cypress test execution speed?

Key factors include: 1) Number of test cases and complexity, 2) Network requests and response times, 3) Test retry configurations, 4) Browser instance management, 5) Resource usage in the application, 6) Command timeout settings, 7) Test parallelization setup.

How can you reduce test execution time in Cypress?

Test execution can be optimized by: 1) Implementing proper test parallelization, 2) Using API calls instead of UI interactions when possible, 3) Optimizing waiting strategies, 4) Implementing proper caching, 5) Reducing unnecessary browser reloads.

What is the role of caching in Cypress tests?

Caching helps improve performance by: 1) Storing browser session data, 2) Caching network responses, 3) Maintaining test artifacts, 4) Preserving application state between tests, 5) Reducing setup time for repeated operations.

How do timeouts affect test performance?

Timeouts impact performance through: 1) Command execution waiting times, 2) Network request timeouts, 3) Page load timeouts, 4) Assert timeouts, 5) Default vs custom timeout configurations. Proper timeout management is crucial for optimal performance.

What is the impact of screenshots and videos on test performance?

Screenshots and videos affect performance by: 1) Increasing disk I/O, 2) Consuming memory resources, 3) Adding processing overhead, 4) Increasing test artifacts size. Consider selective capture and proper configuration for optimal performance.

How does browser instance management affect performance?

Browser management impacts performance through: 1) Browser launch time, 2) Memory usage, 3) Resource allocation, 4) Test isolation overhead, 5) Cache management. Proper browser configuration and reuse strategies can improve performance.

What role does test isolation play in performance?

Test isolation affects performance through: 1) State reset requirements, 2) Setup/teardown overhead, 3) Browser reloads, 4) Database cleanup operations, 5) Session management. Balance isolation needs with performance considerations.

How do network requests impact test performance?

Network requests affect performance through: 1) Response waiting times, 2) Request retry overhead, 3) Payload size processing, 4) Connection management, 5) Stubbing/mocking overhead. Optimize network handling for better performance.

What is the impact of logging on test performance?

Logging affects performance through: 1) I/O operations, 2) Memory usage for log storage, 3) Console output processing, 4) Log file management, 5) Reporting overhead. Implement appropriate logging levels and strategies.

How do retries affect test performance?

Retries impact performance through: 1) Additional test execution time, 2) Resource usage during retries, 3) State reset requirements, 4) Logging overhead, 5) Result aggregation. Balance retry strategies with performance needs.

How can you test authentication flows in Cypress?

Authentication testing involves: 1) Testing login/logout flows, 2) Handling different authentication methods (OAuth, JWT), 3) Testing session management, 4) Verifying token handling, 5) Testing authentication error scenarios, 6) Implementing secure credential management in tests.

What is the best practice for handling sensitive data in Cypress tests?

Sensitive data handling includes: 1) Using environment variables for credentials, 2) Never committing sensitive data to source control, 3) Implementing secure data storage, 4) Proper cleanup of sensitive data after tests, 5) Using encryption when necessary.

How do you test authorization in Cypress?

Authorization testing involves: 1) Verifying role-based access control, 2) Testing permission levels, 3) Checking protected resource access, 4) Testing authorization bypass attempts, 5) Verifying proper access restrictions.

What is CSRF protection and how do you test it?

CSRF testing includes: 1) Verifying CSRF token presence, 2) Testing token validation, 3) Checking token rotation, 4) Testing invalid token scenarios, 5) Verifying protection on sensitive operations.

How can you test SSL/TLS configurations?

SSL/TLS testing involves: 1) Verifying secure connection establishment, 2) Testing certificate validation, 3) Checking protocol versions, 4) Testing mixed content handling, 5) Verifying secure cookie attributes.

What are the basics of XSS testing in Cypress?

XSS testing basics include: 1) Testing input validation, 2) Checking output encoding, 3) Testing script injection scenarios, 4) Verifying content security policies, 5) Testing HTML sanitization.

How do you test secure cookie handling?

Cookie security testing includes: 1) Verifying secure flag presence, 2) Testing HttpOnly attribute, 3) Checking SameSite attributes, 4) Testing expiration handling, 5) Verifying domain restrictions.

What is the importance of testing HTTP headers?

HTTP header testing involves: 1) Verifying security headers presence, 2) Testing CORS headers, 3) Checking content security policies, 4) Testing cache control headers, 5) Verifying X-Frame-Options.

How do you test password policies?

Password policy testing includes: 1) Testing password complexity requirements, 2) Verifying password change flows, 3) Testing password reset functionality, 4) Checking password storage security, 5) Testing password expiration.

What are the basics of input validation testing?

Input validation testing includes: 1) Testing boundary values, 2) Checking special character handling, 3) Testing size limits, 4) Verifying data type validation, 5) Testing sanitization procedures.

What browsers does Cypress support for testing?

Cypress supports: 1) Chrome and Chromium-based browsers (Chrome, Chromium, Edge), 2) Firefox, 3) Electron, 4) Brave. Each browser may have specific configuration requirements and limitations. Chrome is the default browser and provides the most complete feature set.

How do you configure different browsers in Cypress?

Browser configuration involves: 1) Setting browser in cypress.config.js, 2) Using --browser flag in CLI, 3) Configuring browser-specific options, 4) Setting viewport dimensions, 5) Handling browser-specific capabilities. Example: cypress run --browser chrome

What are the common cross-browser testing challenges?

Common challenges include: 1) Different rendering behaviors, 2) Feature support variations, 3) Performance differences, 4) Browser-specific bugs, 5) Different security models, 6) Varying JavaScript implementations, 7) CSS compatibility issues.

How do you handle browser-specific selectors?

Browser-specific selectors require: 1) Using data-* attributes for consistency, 2) Implementing fallback selectors, 3) Handling vendor prefixes, 4) Using browser detection when needed, 5) Maintaining selector documentation for different browsers.

What is viewport configuration in cross-browser testing?

Viewport configuration includes: 1) Setting width and height, 2) Handling responsive breakpoints, 3) Device-specific viewports, 4) Orientation settings, 5) Browser-specific viewport behaviors. Use cy.viewport() command or configuration.

How do you handle browser events across different browsers?

Browser event handling includes: 1) Using browser-agnostic event triggers, 2) Implementing event polyfills when needed, 3) Handling browser-specific event behaviors, 4) Testing event propagation, 5) Verifying event handling consistency.

What are best practices for cross-browser screenshots?

Screenshot best practices include: 1) Consistent viewport settings, 2) Handling dynamic content, 3) Browser-specific capture settings, 4) Proper comparison strategies, 5) Managing screenshot artifacts across browsers.

How do you handle browser capabilities detection?

Capability detection involves: 1) Feature checking, 2) Browser version detection, 3) API support verification, 4) Implementing fallbacks, 5) Managing browser-specific code paths. Use Cypress.browser object for information.

What are common browser compatibility issues?

Common issues include: 1) CSS rendering differences, 2) JavaScript API support, 3) Event handling variations, 4) Performance differences, 5) Security model variations, 6) DOM implementation differences.

How do you handle browser-specific timeouts?

Timeout handling includes: 1) Setting browser-specific timeout values, 2) Handling different performance characteristics, 3) Implementing retry strategies, 4) Managing command timeouts, 5) Browser-specific wait conditions.

How does Cypress support mobile testing?

Cypress supports mobile testing through: 1) Viewport configuration for mobile screen sizes, 2) Mobile event simulation, 3) Touch event handling, 4) Responsive design testing, 5) Mobile-specific selectors and commands, 6) Device orientation simulation.

How do you configure viewport for mobile testing?

Mobile viewport configuration includes: 1) Using cy.viewport() command, 2) Setting specific device presets, 3) Configuring orientation, 4) Handling responsive breakpoints, 5) Testing different screen sizes. Example: cy.viewport('iphone-x') or cy.viewport(375, 812).

What are common mobile testing challenges in Cypress?

Common challenges include: 1) Touch event simulation, 2) Device-specific behavior testing, 3) Performance on mobile devices, 4) Responsive design verification, 5) Mobile gesture handling, 6) Mobile network conditions simulation.

How do you test responsive breakpoints?

Breakpoint testing involves: 1) Using different viewport sizes, 2) Testing layout changes, 3) Verifying content adaptation, 4) Checking media query behavior, 5) Testing element visibility and positioning at different breakpoints.

What are mobile-specific selectors?

Mobile selectors include: 1) Touch-specific elements, 2) Mobile-specific classes, 3) Responsive design selectors, 4) Device-specific attributes, 5) Mobile navigation elements. Consider using data-* attributes for consistent selection.

How do you handle touch events in Cypress?

Touch event handling includes: 1) Using .trigger() for touch events, 2) Simulating tap actions, 3) Handling multi-touch gestures, 4) Testing touch-specific interactions, 5) Verifying touch event responses.

What are best practices for mobile layout testing?

Layout testing practices include: 1) Testing multiple viewport sizes, 2) Verifying element alignment, 3) Checking content overflow, 4) Testing navigation elements, 5) Verifying touch target sizes.

How do you test mobile navigation patterns?

Navigation testing includes: 1) Testing hamburger menus, 2) Verifying swipe navigation, 3) Testing bottom navigation bars, 4) Checking mobile-specific routes, 5) Testing back button behavior.

What are mobile-specific test considerations?

Mobile considerations include: 1) Touch interaction testing, 2) Mobile performance testing, 3) Network condition testing, 4) Device orientation handling, 5) Mobile-specific feature testing.

How do you test mobile-specific features?

Feature testing includes: 1) Touch ID/Face ID simulation, 2) GPS location testing, 3) Camera access testing, 4) Mobile sensor simulation, 5) Mobile storage testing.

Career Essentials

Skill Builder

Confirm Action

Login to Stark.ai

Please Verify Your Phone or Email

Set Learning Alerts

Cypress Interview Questions Your Guide to Success

cypress

What is Cypress and how does it differ from Selenium?

What are the key features of Cypress?

What is the Cypress Test Runner?

How do you install and initialize Cypress in a project?

What is the structure of a basic Cypress test?

What are Cypress commands and how do they work?

How does Cypress handle asynchronous operations?

What are aliases in Cypress and how are they used?

How do you handle assertions in Cypress?

What is the difference between cy.get() and cy.find()?

What are the main types of Cypress commands?

How do you select elements in Cypress?

What are the common interaction commands in Cypress?

How do you type into input fields?

What is the purpose of cy.wait() and when should it be used?

How do you handle dropdowns in Cypress?

What is the difference between .click() and .trigger('click')?

How do you handle checkboxes and radio buttons?

What is the purpose of .within() command?

How do you scroll elements into view?

What is cy.intercept() and how is it used?

How do you make HTTP requests in Cypress?

What is the difference between cy.request() and cy.intercept()?

How do you stub network responses?

What are fixtures and how are they used in API testing?

How do you wait for network requests to complete?

How do you verify request parameters and headers?

What is request aliasing and why is it useful?

How do you handle authentication in API requests?

What are common HTTP status codes and how do you test them?

What is the standard folder structure in a Cypress project?

What are test hooks in Cypress and how are they used?

How do you organize test files in Cypress?

What is the purpose of cypress.config.js?

How do you handle global configuration in Cypress?

What is the role of support files in Cypress?

How do you structure describe and it blocks?

What are custom commands and how are they created?

How do you manage test data in Cypress?

What is the difference between before and beforeEach hooks?

What debugging tools are available in Cypress?

How do you use .debug() command in Cypress?

What is the purpose of cy.log()?

How does Cypress handle test failures?

What is time travel debugging in Cypress?

How do you inspect network requests in Cypress?

What are common causes of flaky tests?

How do you handle timeouts in Cypress?

What is the purpose of screenshots and videos in Cypress?

How do you debug synchronization issues?

How do you integrate Cypress with CI/CD pipelines?

What is the difference between cypress open and cypress run?

How do you configure test reporting in CI/CD?

What are environment variables in Cypress CI/CD?

How do you handle test artifacts in CI/CD?

What is parallel test execution in Cypress?

How do you handle test retries in CI/CD?

What is the Cypress Dashboard service?

How do you manage test data in CI/CD?

What is the importance of CI/CD pipeline caching?

What are the key principles of writing good Cypress tests?

What is the Page Object Pattern and how is it implemented in Cypress?

What are best practices for selector strategies in Cypress?

How should you structure your test files?

What is the AAA (Arrange-Act-Assert) pattern?

How should you handle test data management?

What are best practices for writing assertions?

How should you handle authentication in tests?

What are best practices for using custom commands?

How should you handle waiting in tests?

What factors affect Cypress test execution speed?

How can you reduce test execution time in Cypress?