To see Cypress results as a test run executes, use its default spec reporter, which writes progress and results to standard output (STDOUT). For JUnit XML as well as terminal output, select the built-in JUnit reporter and set toConsole=true. To keep a hosted run history with results and artifacts, configure Cypress Cloud and run Cypress with --record.
Choose where Cypress results should go
| What you need | Use | Setup |
|---|---|---|
| Live progress and a pass/fail summary in a terminal or CI log | Default spec reporter |
Run cypress run; no reporter change is needed. |
| Human-readable output plus a machine-readable report file | JUnit reporter | Set mochaFile and toConsole=true. |
| Shared hosted run history and related artifacts | Cypress Cloud | Configure a Cloud project and record key, then run with --record. |
These paths solve different problems. Reporter output appears in the process log; Cloud recording sends run data to a hosted service. Cloud is not required to print test results to standard output.
Stream readable results to the terminal or CI log
Cypress uses Mocha reporters. Its default spec reporter writes information to STDOUT, so the shortest route is simply:
npx cypress runIn a CI job, the output is available in that job’s log as Cypress runs. If you have configured another reporter, specify spec explicitly:
#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
npx cypress run --reporter specCypress also supports custom Mocha reporters. Choose one based on the output your terminal or downstream tooling needs; the reporter controls Cypress-side output, while a CI vendor’s steps for importing or publishing reports are specific to that vendor.
Write JUnit XML and show the output in the console
The built-in JUnit reporter can print results while writing an XML file. Use toConsole=true for terminal output and mochaFile for the report destination:
Rank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
npx cypress run --reporter junit --reporter-options "mochaFile=results/my-test-output.xml,toConsole=true"Make sure the output directory exists or is otherwise writable in the job environment. Adapt the path to the artifact location your CI system collects. The command configures Cypress to create XML; it does not by itself tell a CI vendor to ingest or publish that XML.
Configure JUnit in Cypress configuration
Instead of passing reporter options on every command, put them in the project’s Cypress configuration. For example, in a JavaScript configuration file:
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 problemsRank #3
- Clear visuals. Fluid motion: A 144Hz refresh rate and 1ms MPRT deliver smooth, tear‑free motion across work, gaming, and streaming for clearer, more fluid viewing.
- Eye comfort: TÜV Rheinland 3‑star* certification reduces harmful blue light while preserving stunning color quality without compromise. *TÜV Rheinland 3-star eye comfort certification.
- Wide viewing angle: Get consistent views across a wide 178° /178° viewing angle.
- In-Plane Switching (IPS): See excellent color accuracy and consistency across wide viewing angles with In-plane Switching (IPS) technology.
- Ultra-thin bezels: Maximize your viewing experience with thin bezels.
const { defineConfig } = require('cypress');
module.exports = defineConfig({
reporter: 'junit',
reporterOptions: {
mochaFile: 'results/my-test-output.xml',
toConsole: true,
},
});Use the configuration style appropriate to your project’s existing setup. The CLI form is convenient for a one-off run; project configuration makes the choice part of the checked-in test setup.
Keep reports from multiple spec files
A static XML filename can be overwritten as Cypress runs multiple spec files, leaving only the final spec’s report. If you need every spec’s result, configure a per-spec filename using the JUnit reporter’s [hash] token, then merge the generated reports with the merger you use in your build. The exact merge command depends on that tool, so verify its syntax and configure your CI artifact collection for the resulting files.
Rank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
Record a run in Cypress Cloud
For a hosted view of test runs, set up a Cypress Cloud project and obtain its record key. Then pass the key when recording:
npx cypress run --record --key <record-key>In CI, the key can instead be made available through the CYPRESS_RECORD_KEY environment variable, avoiding a literal key in the command. Treat it as a secret: use your CI system’s secret-variable facility rather than committing it to the repository.
Recommended Free Tools
Best Value
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
Cloud recording requires the project and key to be configured; --record is not a replacement for local reporter configuration. Cloud run pages organize information at run, test, and spec levels, and can surface Cypress standard output according to the configured reporter. Screenshots and videos can be attached to test results, with recorded-run artifacts available to browse or download. See the Cypress Cloud setup guide and recorded-runs documentation for current setup and run views.
Understand what recording can include
Recorded-run data can include terminal standard output, test results and definitions, Cypress configuration excluding Cypress environment variables, screenshots, videos, and CI- or Git-related OS environment variables. With Test Replay enabled, additional debugging data can include rendered DOM and CSS, Cypress command events, network traffic, and browser console logs. Review Cypress’s Cloud FAQ and data storage and controls for the current data handling details relevant to your project.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Capture screenshots or video alongside results
During cypress run, Cypress takes screenshots on test failure by default unless that behavior is disabled. Video recording is disabled by default; enable it with video: true in Cypress configuration when you want videos. Video is recorded per spec, so account for that when deciding which artifacts to retain. The official screenshots and videos guide documents the current settings.
Troubleshoot missing or incomplete output
- No progress in the CI log: confirm the job is running
cypress runand that the reporter isspecor another reporter that writes to the console. JUnit needstoConsole=truefor console output. - JUnit XML exists but the console is quiet: add
toConsole=truetoreporterOptionsor the CLI reporter-options string. - Only one XML report remains after several specs: replace the shared static filename with a per-spec filename using
[hash], then merge the files if a single report is needed. - No XML artifact is available in the CI interface: check that the configured directory is writable and that the CI job is configured to collect or publish that path. Cypress creates the report; artifact ingestion is configured in the receiving CI product.
- Cloud does not show a recorded run: confirm the project setup, record key, and
--recordflag. In CI, check thatCYPRESS_RECORD_KEYis present in the job environment. - No video appears: enable
video: true; video is off by default. For failure screenshots, check that screenshot capture has not been disabled.
Or skip the browser setup
If your goal is to capture a website screenshot rather than stream Cypress test output, ScreenshotNeo is a separate website screenshot API and MCP server. A single GET request returns an image or PDF; for example:
Free tools Windows power users keep installed
One-click scans. No signup required.
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 for parameters and response details. It can remove cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are not billed. Its MCP server lets AI agents take screenshots, and the free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for free ScreenshotNeo access.
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.
