Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use the Cypress Test Runner and terminal output for local diagnosis, emit a structured report such as JUnit XML for your CI provider, retain screenshots or video for failures, and add Cypress Cloud when you need a searchable history across runs. These layers work together: a JUnit report can feed CI annotations while screenshots remain available as artifacts and Cloud tracks trends.
Choose the visibility layer that solves your problem
| Need | Use | What you gain |
|---|---|---|
| Understand what happened during a local test | Cypress app and default spec reporter |
Command log, failure context, and terminal output for the current run |
| Show individual outcomes in the CI interface | JUnit XML or another report format supported by your CI provider | Structured results the CI system can ingest; ingestion must be configured in that provider |
| Share a standalone report | Mochawesome JSON merged into an HTML report | A report file that can be retained or shared outside the terminal |
| Inspect a failure after the job ends | Retained screenshots and optionally video | Visual evidence from the failing run, provided CI preserves the files |
| Compare runs and investigate trends | Cypress Cloud recorded runs | Centralized run history, artifacts, and historical views for failed, flaky, and modified tests |
These options are complementary rather than exclusive. Pick the smallest combination that answers your team’s questions, then add another layer only when you need its distinct evidence or history.
As an Amazon Associate I earn from qualifying purchases.
Improve local diagnosis first
Cypress uses the spec reporter by default and writes its output to standard output (STDOUT). Run tests in the Cypress app when you need to inspect their progress interactively; use the command log and reporter output to follow the failing test and its context. The official Cypress reporters guide documents the default and alternative reporters.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteIf a failure is intermittent, record enough context to distinguish a test assertion failure from a page that failed to load or a timing problem. A concise, reproducible test and its failure output are often more useful than a large report that does not preserve the underlying context.
Send structured results to CI
When a CI interface needs to show individual test outcomes, configure Cypress to emit JUnit XML and configure the CI provider to ingest that report. Cypress documents junit as a built-in reporter; teamcity is another built-in option. Since Cypress is built on Mocha, other Mocha reporters can also be used. The exact ingestion step depends on your CI provider, so follow that provider’s instructions for discovering and displaying JUnit files.
Prevent a multi-spec report from being overwritten
A static JUnit output filename can be overwritten as Cypress processes multiple spec files, leaving only the last spec’s report. Use a unique filename pattern such as [hash] for per-spec output, then merge the generated files if your CI workflow expects one report. Confirm the reporter’s filename pattern and merge behavior in the reporter documentation before adopting it.
For a standalone HTML report, Cypress’s reporter guide demonstrates a Mochawesome workflow: generate JSON reports per spec, merge them with mochawesome-merge, and generate HTML with marge. Avoid configuring every spec to write to the same static JSON filename, for the same overwrite reason.
Free tools Windows power users keep installed
One-click scans. No signup required.
Keep screenshots and video after the run
Screenshots
In cypress run, Cypress automatically captures screenshots when tests fail. The default screenshot folder is cypress/screenshots; you can change the configured folder. Failure screenshots are not automatically taken during cypress open. See the screenshots and videos guide for configuration details.
Video
Video recording is disabled by default. When enabled, Cypress records video per spec during cypress run, not during cypress open. Video files go to the configured videos folder.
CI artifact retention
Capturing a file is not the same as retaining it. Configure the CI job to collect and retain the screenshots and, if enabled, videos from the Cypress output folders. Cypress clears the screenshots and video folders before a run by default. If your workflow depends on files already in those folders, check the trashAssetsBeforeRuns behavior and plan retention deliberately.
Rank #4
Add Cypress Cloud when you need run history
Cypress Cloud records runs when Cypress is invoked with --record and a record key. Its documented recorded data includes test results, terminal output, screenshots, and videos. Cloud also provides historical views for failed, flaky, and modified tests. The recorded runs documentation explains the workflow and available run information; the Cloud FAQ covers common questions.
Cloud is most relevant when you need centralized history or artifacts across CI runs, not merely a pass/fail result for one job. Consider the hosted workflow alongside your plan limits and data-handling obligations before enabling recording.
Best Value
Review data handling before recording
Recorded runs can include CI and Git-related metadata as well as test output and artifacts. Cypress documents storage and masking controls in its data storage and masking guide. Review what your tests may expose—such as sensitive page content—and decide whether recording is appropriate for your environment.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use UI Coverage only for a coverage question
UI Coverage is a separate layer for mapping UI coverage across pages and components from Cypress runs. Cypress documents setup through Cypress Cloud with Test Replay and describes monitoring changes through a Results API. It addresses which parts of a user interface are covered, not ordinary test pass/fail reporting. See the UI Coverage setup guide.
Troubleshoot missing or unhelpful results
- CI shows only a summary: Check that Cypress is producing the expected report file and that your CI provider is configured to ingest it. A reporter alone does not configure the CI interface.
- The report contains only one spec: Check for a static per-spec output filename being overwritten. Use unique filenames, then merge outputs if needed.
- No screenshot appears: Confirm the failure occurred in
cypress run, then check the configured screenshot folder and whether the CI job collects that folder. Screenshots are not automatic incypress open. - No video appears: Video is off by default; enable it for run mode and confirm the configured video folder is retained as a CI artifact.
- Earlier files disappear: Cypress clears screenshot and video folders before runs by default. Review
trashAssetsBeforeRunsand your artifact strategy. - Cloud has no run history: Confirm the run uses
--recordand a record key, then consult Cypress’s recorded-run documentation for setup.
Consider community reporters only for a specific need
Cypress’s plugins catalog lists integrations including allure-cypress, cypress-terminal-report, cypress-mochawesome-reporter, and ReportPortal’s Cypress agent. They are community options, not endorsements. Before adopting one, check current maintenance, compatibility with your Cypress version, and the CI setup it requires. The Cypress plugins catalog is the starting point.
Recommended Free Tools
Or skip the browser setup
ScreenshotNeo does not replace Cypress reporting, JUnit ingestion, or Cloud run history. It can provide a separate screenshot of a page when you need visual context around a test failure without setting up browser automation for that capture.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://your-app.example -o shot.webpSee the ScreenshotNeo API documentation for request options. It accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server offers screenshot and PDF tools for AI agents. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. ScreenshotNeo is made by Yorker Media; see ScreenshotNeo for service details.
Sign up for 1,000 free screenshots a month, with no card required.
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.
