Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesThe right Cypress plugin depends on the gap in your end-to-end suite: use @testing-library/cypress for user-oriented DOM queries, cypress-axe for automated accessibility checks, cypress-real-events for native-style interactions, or a coverage, filtering, or Gherkin integration when you need those workflows. These are not interchangeable, and most are independently maintained npm packages rather than built-in Cypress features.
Choose by the problem your tests need to solve
There is no evidence here for a universal quality ranking or independent head-to-head plugin test. Start with the behavior or reporting need, then check ownership, maintenance, setup requirements, and compatibility with the Cypress version installed in your project. Cypress’s plugin directory distinguishes official entries from community packages and says community plugins are not reviewed by Cypress.
| Need | Option | What it adds | Important caveat |
|---|---|---|---|
| Find elements by user-visible roles, labels, or text | @testing-library/cypress |
Testing Library DOM queries, including findBy and findAllBy, as Cypress commands. |
Import its Cypress commands and verify package support for your installed versions. |
| Run automated axe-core accessibility checks | cypress-axe |
A community plugin for checking applications for accessibility issues with axe-core. | Community-owned; automated results need human review. |
| Get managed accessibility reporting integrated with Cypress Cloud | Cypress Accessibility | A hosted service reporting on unique states reached in E2E and component tests, with results and CI integration. | A separate paid Cypress Cloud solution, not an npm plugin; check current plan terms. |
| Exercise hover, swipe, or other native-style browser events | cypress-real-events |
Fires native system events for interaction cases that ordinary Cypress commands may not represent the way your test requires. | Community project; check its declared Cypress version range and maintenance. |
| Author tests in Gherkin/Cucumber | Community Cucumber preprocessor plugin | Enables a Gherkin-based authoring workflow. | Cypress says Cucumber is not officially supported; it adds workflow complexity. |
| Measure code coverage | @cypress/code-coverage |
Coverage support for E2E, unit, and full-stack coverage workflows. | Typically requires application instrumentation; setup depends on the project. |
| Filter specs by title or tags | @cypress/grep |
Title and tag filtering; Cypress’s directory labels this an official entry. | Confirm current version compatibility in package metadata. |
How do I add Testing Library to Cypress?
The integration adds Testing Library query commands to Cypress; it does not replace Cypress’s test runner. Cypress’s FAQ specifically points users to @testing-library/cypress and query methods such as findByRole, findByLabelText, findByText, and findByTestId.
- Check the package’s current installation instructions and compatibility against your installed Cypress version. The integration documentation was last updated November 26, 2023, so do not assume its instructions or package support have remained unchanged.
- Install
@testing-library/cypressas a development dependency using your project’s package manager. - Import the package’s Cypress commands from the project’s Cypress support file, following the current package instructions.
- Use its query commands in tests to locate elements by roles, accessible labels, visible text, or other supported queries; run the suite to confirm the commands load in your project configuration.
Prefer queries that reflect how a person identifies an interface element where practical. A test ID can still be useful when the interface offers no meaningful user-facing selector.
Which Cypress plugin should I use for accessibility?
Use cypress-axe for in-test automated checks
cypress-axe is the community option in this shortlist for running axe-core accessibility checks from Cypress tests. Validate its package maintenance and compatibility before adopting it. Automated checks can identify some issues, but they do not establish that an interface works well for every disabled user or with every assistive technology.
Use Cypress Accessibility when you need managed reporting
Cypress Accessibility is a separate Cypress Cloud service, not the same product as the community cypress-axe package. Its documentation describes reports on unique states reached during E2E and component testing, with CI integration. Cypress advises complementing automation with human judgment, managing false positives, and checking assistive-technology support. The Cypress App is free and MIT-licensed; Cloud billing, Accessibility, and UI Coverage are separate offerings. Verify current availability and pricing directly before deciding.
Which plugin supports hover or swipe?
cypress-real-events is the community plugin in the directory for native system events, including use cases such as hover or swipe. It is a candidate when the distinction between a Cypress-simulated interaction and a native-style browser event matters to the test. Check the package’s declared Cypress compatibility and maintenance; do not assume a community package supports every current Cypress release.
When do Cucumber, coverage, or filtering plugins make sense?
Cucumber: adopt Gherkin only for a real team need
A community Cucumber preprocessor can support Gherkin authoring, but Cypress says Cucumber is not officially supported and that this approach introduces workflow complexity. It is most defensible when product, QA, and engineering teams will genuinely share feature specifications—not merely because Gherkin is familiar.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Coverage: plan for instrumentation
@cypress/code-coverage is the plugin identified by Cypress for E2E, unit, and full-stack coverage. Coverage is not just a reporter switch: application instrumentation is commonly part of the setup. Follow the current guide for your build and test configuration.
Filtering: use title or tag selection deliberately
@cypress/grep is listed as an official option for filtering specs by title or tags. Check its current package metadata and Cypress compatibility, and make sure CI still runs the complete intended suite rather than silently omitting tests.
How to evaluate a Cypress plugin before installing it
- Ownership: determine whether Cypress labels the entry official or community. Community status means Cypress does not review the plugin.
- Compatibility: inspect the package’s supported Cypress versions and dependencies, then compare them with your project’s pinned version.
- Maintenance: review release activity, issue handling, and documented setup before relying on the plugin in CI.
- Setup burden: identify required support-file imports, application instrumentation, preprocessors, or Cloud configuration.
- Interpretation: decide whether output needs human judgment, as with accessibility findings, or whether the plugin can directly drive a reliable pass/fail assertion.
- Cost and licensing: distinguish free/open-source npm software from paid hosted Cypress Cloud services; verify current service terms rather than relying on old prices.
The release page showed Cypress 16.1.1, released September 29, 2026, as the latest release checked for this article; Cypress 16.0.0 was released September 1, 2026. That does not establish compatibility for every community plugin. Recheck package metadata at the time you install. Cypress tests browser-based applications, including responsive layouts and mobile web views; it does not run native mobile apps.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Capture screenshots outside the plugin shortlist
ScreenshotNeo is a separate website screenshot API and MCP server, not a Cypress plugin or a substitute for Cypress assertions. It can be useful when a workflow also needs a clean screenshot or PDF from a URL. Its cleanup options accept consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be disabled. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and responses report page verdict and billing headers. AI agents can use its MCP server tools to take screenshots, get page information, and capture PDFs. The ScreenshotNeo docs cover the API.
Recommended Free Tools
Or skip the browser setup: One GET request returns a screenshot; replace the example URL with the page you want to capture and supply your API key.
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpCookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
