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 glitchesUse the right combination of Cypress’s local Test Runner, a CI-readable report, retained failure screenshots or video, and—when you need run history—Cypress Cloud. These layers solve different problems: a reporter makes outcomes easier to consume, artifacts help explain a failure, and Cloud organizes results across recorded runs. You can combine them rather than choosing just one.
Choose the visibility layer that matches the problem
| What you need | Use | What it gives you |
|---|---|---|
| Understand a failure while developing | Cypress app and default spec reporter |
In-app command progress and terminal output for the current run. |
| Show individual test outcomes in CI | JUnit reporter plus your CI provider’s report ingestion | Structured XML that a configured CI system can display or annotate. |
| Share a standalone report | Mochawesome JSON, merge, and HTML generation | A generated report file for a run, with per-spec files combined when needed. |
| Inspect a failed test after CI finishes | Failure screenshots and optionally video, retained as CI artifacts | Visual evidence of the page and, when enabled, a per-spec recording. |
| Compare runs and inspect historical patterns | Cypress Cloud recorded runs | Centralized results and artifacts, plus historical views for failed, flaky, and modified tests. |
These approaches are compatible: for example, a team can publish JUnit results in its CI interface, retain screenshots, and record runs to Cypress Cloud. The practical choice depends on whether the missing information is current-run detail, shareable output, failure evidence, or history.
Diagnose a test locally
Cypress uses the spec reporter by default and writes its output to standard output. Run tests in the Cypress app when you need to watch command progress and inspect the failure in context; use the terminal output to identify the spec, test, and failure reported by the run. See the Cypress reporters documentation for reporter behavior and configuration.
The default reporter is often enough for an individual developer. If the terminal summary is not the problem but a failure is hard to understand after the run, add retained screenshots or video rather than changing reporters alone.
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 →Publish test outcomes to CI
For a CI interface that can ingest JUnit XML, configure Cypress’s JUnit reporter and then configure the CI provider to collect the generated report. Cypress documents the reporter and its CLI configuration, but ingestion and presentation steps vary by CI provider, so follow that provider’s report or artifact instructions as well.
Watch for overwritten reports
A static JUnit output filename can be overwritten when Cypress runs multiple spec files. The final file may then represent only the last spec rather than the entire run. Use unique output filenames, such as a pattern containing [hash], and merge outputs if your reporting workflow requires one combined report. Verify that the CI job collects all generated files.
When you need a standalone HTML report
Cypress’s reporter guide demonstrates a Mochawesome workflow: write JSON results per spec, merge them with mochawesome-merge, then generate HTML with marge. The key operational detail is to avoid a shared static per-spec filename, which can discard earlier results through overwrite. Check the reporter guide for the current configuration example and ensure your CI job retains the generated HTML and any intermediate files you need.
Cypress also includes teamcity and junit reporters, and supports custom Mocha reporters because Cypress is built on Mocha. Community integrations listed in the Cypress plugins catalog include allure-cypress, cypress-terminal-report, cypress-mochawesome-reporter, and ReportPortal’s Cypress agent. Treat these as integration options, not endorsements; check current maintenance, Cypress compatibility, and CI requirements before adopting one.
Free tools Windows power users keep installed
One-click scans. No signup required.
Keep screenshots and video from failed runs
During cypress run, Cypress automatically captures screenshots when a test fails. Screenshots go to cypress/screenshots by default, unless the configured screenshots folder changes. Video is disabled by default; when enabled, Cypress records video per spec during cypress run and saves it to the configured videos folder. Neither failure screenshots nor video are automatically captured during cypress open. The screenshots and videos guide covers configuration and behavior.
Preserve the files in CI
- Run the suite in run mode so the run can create failure screenshots and, if enabled, video.
- Configure your CI provider to collect the configured screenshots and videos folders as artifacts, including the retention period your team needs.
- Check the artifact upload step after both passing and failing jobs; a report that refers to files the job discarded is not useful for later diagnosis.
Cypress clears screenshots and video folders before a run by default. If your workflow expects files from an earlier run to remain, check the trashAssetsBeforeRuns behavior and configure retention deliberately. For normal CI diagnosis, upload artifacts from the current run rather than relying on files left in the workspace.
Rank #4
Use Cypress Cloud for centralized run history
Cypress Cloud records CI runs when Cypress is invoked with --record and a record key. Its recorded-run documentation lists test results, terminal output, screenshots, and videos among recorded data. Cloud also provides historical views for failed, flaky, and modified tests. Review the recorded runs documentation and Cypress Cloud FAQ for the workflow and product details.
Cloud is a fit when separate job artifacts and one-run reports do not provide the history or centralized view your team needs. It is a hosted workflow, so consider plan limits and data handling as well as convenience. Cypress’s FAQ says recorded runs can include CI and Git metadata alongside test output and artifacts. Review Cypress Cloud data storage and masking and your organization’s obligations before recording tests that may expose sensitive content. Product documentation describes available controls; it does not establish a specific performance improvement for every team.
Best Value
Separate UI coverage from ordinary test reporting
If the question is which pages or components your tests cover—not why a particular test passed or failed—Cypress UI Coverage is a distinct visibility layer. Cypress documents setup using Cypress Cloud with Test Replay and describes monitoring changes through a Results API. See the UI Coverage setup guide. For routine pass/fail visibility, begin with the reporter and artifact options above instead.
Or skip the browser setup
When your goal is a clean screenshot of a website’s rendered state rather than Cypress test-run reporting, ScreenshotNeo is a separate screenshot API and MCP server; it does not replace Cypress reporters, test artifacts, or Cloud history. One GET request returns an image or PDF. The following cURL example saves a WebP capture of Stripe; replace the URL with the page you want to capture. See the ScreenshotNeo API documentation for options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, with response headers indicating the page verdict and billing status. Its MCP server offers screenshot and PDF tools for AI agents. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Frequently Asked Questions
Can JUnit reporting and Cypress Cloud be used together?
Yes. They address different destinations: a CI provider can ingest JUnit XML while Cloud records runs for centralized history.
Does UI Coverage replace Cypress pass/fail reports?
No. UI Coverage addresses which UI areas tests exercise; reporters and run artifacts address outcomes and failure diagnosis.
Quick Recap
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.
