Cypress UI Coverage helps you find where an existing end-to-end or component-test suite has not exercised interactive UI. Use its report to locate an uncovered view or control, decide which gap matters to a user journey, add a test with meaningful outcome assertions, then rerun and review the report. It can speed up discovery and prioritization; it does not guarantee faster test authoring or make AI-generated tests correct without review.
How do I find missing Cypress tests?
Open UI Coverage for a recorded Cypress Cloud run. The report analyzes pages visited by end-to-end tests and mounted components in component tests. It captures DOM-state snapshots, identifies interactive elements, and shows which of those elements Cypress interactions exercised. End-to-end results are generally organized into views based on URL patterns; component-test views are generally organized by spec file. See Cypress’s UI Coverage overview and Views documentation.
As an Amazon Associate I earn from qualifying purchases.
- Start with the views and controls that matter. Scan for low-coverage views, untested elements, and untested links. Prioritize a consequential journey in your own application—such as sign-in, checkout, or account changes only if those flows exist—rather than chasing the report’s lowest percentage by default.
- Inspect untested links. Cypress can surface views never visited in the run by discovering links to them on pages that were tested. Check whether each destination is an owned, in-scope page before treating it as a test gap.
- Find the relevant spec and choose a scenario. Write a test around a user outcome, not a click whose only purpose is to raise coverage. For example, after submitting a form, assert the expected success state or validation message.
- Rerun and inspect. Confirm that the expected element or view is now covered, and review the test itself for meaningful assertions and maintainable selectors.
A view’s score is the percentage of its interactive elements tested. The overall score divides tested interactive elements by all interactive elements in included views, so larger views contribute more to the total. Use these scores as a triage map, not as a standalone quality target: interaction coverage does not establish that assertions check the right behavior.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Can Cypress generate tests for uncovered UI?
Cypress promotes AI test-case generation based on a customer’s Cypress projects. Its Cloud MCP integration can make UI Coverage data available to an AI agent, which can surface risky untested views and point to the appropriate spec file. Cypress announced this capability on April 28, 2026, describing the goal as: “Ask your AI agent what your tests never cover, not just what’s failing.” The announcement does not quantify time saved or independently establish the correctness of generated tests. See Cypress’s Cloud MCP announcement.
Treat generation as a starting point. Before merging a generated or assisted test, check that it:
- sets up the state and data needed for a reproducible scenario;
- uses selectors that are stable and understandable;
- asserts the user-visible result, not just that an action completed;
- adds a distinct behavior check rather than duplicating an existing test; and
- fits the project’s conventions and can be maintained when the UI changes.
UI Coverage helps identify where to investigate; the team still decides what behavior deserves a test and whether the test proves it.
How to turn a coverage gap into a useful test
- Confirm scope. Follow the untested link or inspect the uncovered element. Decide whether it belongs to an application flow the team intends to test. A third-party destination or intentionally excluded widget may be out of scope.
- Describe the user outcome. State what should happen, including the relevant starting condition. This keeps the test focused on behavior rather than on coverage percentage.
- Update the appropriate spec. Add or revise the test where related scenarios already live. Prefer selectors and setup that are consistent with the project.
- Assert the result. Verify the resulting state, message, navigation, or other expected behavior. A successful click alone is not evidence that the user journey worked.
- Run the test and record a new Cloud run. Review the UI Coverage report against the intended gap. If the report disagrees with the observed test behavior, investigate recognition and configuration before changing tests just to alter the score.
What UI Coverage can—and cannot—tell you
| Approach | What it reveals | What to keep in mind |
|---|---|---|
| Cypress UI Coverage | Pages, states, links, and interactive elements encountered in Cypress runs, with a view of interactions the report recognizes as tested. | It is a separately purchased premium solution, not included in standard Cypress Cloud plans according to Cypress’s product page. Confirm current plan terms with Cypress. A higher score does not prove assertion quality. |
| Traditional code coverage | Source-code execution, such as covered files, lines, or statements. | It offers a code-oriented view and does not directly map unexercised user-facing controls. Cypress presents UI Coverage as a complementary perspective, not a reason to discard code coverage. |
| Manual review of specs and requirements | Whether tests and assertions address intended behaviors and risks. | It requires human review and does not automatically provide the same page-and-element map. |
When choosing how to find gaps, consider the cost and availability of the approach, the granularity of the gaps it identifies, compatibility with your existing test stack, how it handles out-of-scope UI, and whether reports fit your CI or AI-agent workflow. Cypress says its UI Coverage reports can be used in CI workflows for thresholds or build responses; that is a workflow capability, not evidence that a particular threshold improves quality. Cypress’s product page also publishes a customer testimonial reporting a 35% increase in test coverage within two weeks and 1–2 hours saved per QA team member per week. Those are results attributed to Vistar Media’s Director of Quality Assurance, not an independently validated or typical outcome.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsWhy a coverage score may mislead
A low score is a signal to investigate, not necessarily a list of missing tests. Cypress’s troubleshooting documentation describes several reasons reports can diverge from a team’s expectations:
- Controls appear more than once. If identifying attributes vary between snapshots, the same apparent control may be represented multiple times. Use stable identifiers and review
significantAttributesorattributeFilterswhere appropriate. - Different controls are merged. Overly generic identifiers can make distinct elements look alike. Review element grouping and the attributes used to identify controls.
- An interaction is not counted. The report may not recognize a command used by the test. Check the supported interaction model and declare additional interaction commands where appropriate.
- Out-of-scope UI lowers the score. Third-party widgets and links outside the testing goal can affect results. Use view filters or other documented configuration to exclude genuinely out-of-scope UI, not owned pages merely to improve a number.
- Dynamic URLs create redundant views. Review view grouping so equivalent pages are not needlessly split into separate views.
Configuration changes do not rewrite an already processed report. Cypress warns: “Every run is processed with the configuration that was saved at that moment, so edits you make afterward don’t change an existing report until you reprocess it.” After changing configuration, regenerate the report before evaluating whether the change worked. Consult Cypress’s UI Coverage troubleshooting guide.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your work also needs clean screenshots of application pages for documentation or review, ScreenshotNeo is a website screenshot API and MCP server. Its separate service does not generate Cypress tests or replace UI Coverage. One GET request captures a URL as an image or PDF:
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation. It accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify the page verdict and billing status in headers. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Sign up for ScreenshotNeo’s free plan.
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.
