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.
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.
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.
Handle dependencies through proper test isolation, setup hooks, and dependency injection. Consider implementing modular test setup, proper cleanup procedures, and avoiding shared state between tests.
Use fixtures or external data sources for test data, implement test iteration over data sets, and proper data validation. Consider implementing data generation utilities and proper data cleanup strategies.
Document tests using clear descriptions, proper comments, and meaningful test names. Consider implementing documentation generation tools, maintaining test documentation, and proper test organization for clarity.
Break down complex workflows into smaller, reusable steps, implement proper state management, and maintain clear test organization. Consider implementing workflow abstractions and proper error handling strategies.
Create custom tasks using Cypress task API, implement specific task runners, and handle complex automation needs. Consider implementing proper error handling, logging, and integration with build processes.
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.
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.
Context can be shared using aliases, custom commands, shared fixtures, or test hooks. Use cy.wrap() for complex objects, and consider implementing proper cleanup to prevent test pollution. Avoid sharing state when possible to maintain test independence.
Configure test retries in cypress.config.js, implement robust selectors and assertions, and use proper waiting strategies. Consider implementing custom retry logic for specific scenarios and proper logging for debugging flaky tests.
Large test suites can be organized by feature, domain, or test type. Implement proper folder structure, use tags for test categorization, and consider implementing test run strategies for efficient execution.
Implement browser-specific configurations, use proper feature detection, and handle browser differences in custom commands. Consider implementing browser-specific test suites and proper browser compatibility testing strategies.
Implement proper test isolation, handle shared resources, and configure parallel test execution. Consider implementing proper test grouping, resource management, and execution strategies for parallel runs.
Create custom reporters using Mocha reporter API, implement plugins using Cypress plugin API, and handle specific reporting needs. Consider implementing custom logging, reporting formats, and integration with external tools.
Handle complexity through proper abstraction, modular test design, and clear organization. Consider implementing design patterns, proper documentation, and maintainable test structures.
Create custom test orchestration using Cypress APIs, implement specific execution flows, and handle complex test scenarios. Consider implementing proper orchestration patterns, control flows, and execution management.
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.
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', () => {...}); });
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.
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.
Page Objects can be implemented as classes or objects that encapsulate page elements and actions. Store them in support/pages directory, export as modules, and import in test files. They improve maintainability by centralizing page-specific code and reducing duplication.
Optimize test suites through proper test organization, efficient resource usage, and performance improvements. Consider implementing test prioritization, proper caching strategies, and execution optimization.
Create custom test frameworks using Cypress APIs, implement specific testing patterns, and handle unique testing needs. Consider implementing proper framework design, documentation, and maintenance strategies.
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.
Environment variables can be managed through cypress.env.json, cypress.config.js, or command line arguments. Use Cypress.env() to access variables, avoid committing sensitive data, and implement proper environment-specific configurations.
Use environment-specific configuration files, environment variables, and conditional logic in tests. Consider implementing environment-specific commands, baseUrl configurations, and proper test data management for different environments.
Maintain test suites through proper code organization, regular updates, and efficient refactoring. Consider implementing maintenance schedules, update strategies, and proper version control practices.
