Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsTo inspect Cypress test activity, run npx cypress open and use the Test Runner’s Command Log; for Cypress startup or process diagnostics, set a targeted DEBUG namespace in the terminal. Browser DevTools, screenshots, videos, and Cypress Cloud Test Replay provide other evidence depending on where a failure occurs.
View commands and snapshots in Cypress open mode
- From your project directory, run
npx cypress open, open the relevant spec, and run or select a test. - Use the Command Log in the Test Runner to follow commands and hooks in order. Expand a test to see its command entries, including setup and teardown hooks.
- Hover over a command to return the application preview to the state captured for that command. Cypress documents a default buffer of 50 tests’ worth of snapshots and command data. See Cypress open mode.
The Command Log also shows page events such as XHR and fetch requests, hash changes, page loads, and form submissions. If requests clutter the display, use the “Show HTTP Requests” toggle to hide those entries. This changes what is shown in the log; requests still execute and remain available to assertions and tools such as cy.intercept().
As an Amazon Associate I earn from qualifying purchases.
Inspect a command in browser DevTools
Keep the browser’s Developer Tools open and click a Command Log entry. Cypress writes structured details to the browser console, such as the command issued, its yielded value, elements found, and selector used. This can show what a query or action received without adding temporary logging to the test.
For a failing command, read the error, code frame, and stack trace in the Runner, then inspect the surrounding Command Log entries. Cypress’s debugging guide recommends using browser developer tools alongside the Cypress interface; source maps help relate stack traces to project source files.
Check timing failures against the command sequence
If a test appears timing-sensitive, verify that the required network response or DOM state is ready before the assertion runs. Prefer synchronizing with the relevant request or state—using aliases where appropriate—rather than adding arbitrary delays. The order and snapshots in the Command Log can help identify where the expected state diverged.
Add structured details for custom commands
Cypress.log() controls entries created for custom commands. Its consoleProps option supplies structured details shown in DevTools when the entry is clicked; autoEnd: false is available when a command completes asynchronously. See the Cypress.log() API.
Be deliberate about what you return through consoleProps. Cypress examples include response bodies, user IDs, session tokens, and form values; avoid logging secrets or sensitive user data.
Free tools Windows power users keep installed
One-click scans. No signup required.
Enable Cypress terminal debug logs
Set DEBUG before launching Cypress. For broad diagnostics on macOS, Linux, or Windows Git Bash with npm, run:
DEBUG=cypress:* npx cypress runUse npx cypress open in place of run when diagnosing startup while opening the Specs UI. The full cypress:* namespace can produce a large volume of output and affect performance, so enable it only as needed and narrow it to the subsystem involved. Examples documented by Cypress include:
DEBUG=cypress:server:projectfor project opening.DEBUG=cypress:server:browsers*for browser detection.DEBUG=cypress:server:reporterfor reporter issues.DEBUG=cypress:server:videofor video recording.
Namespaces can be combined with commas; a leading hyphen excludes a noisy source. Cypress lists equivalent environment-variable forms for Yarn, pnpm, and Bun in its Troubleshooting: Cypress App guide. For Windows CMD, set the variable before the Cypress command:
set DEBUG=cypress:*In PowerShell, use:
$env:DEBUG='cypress:*'Turn on browser-side Cypress driver logs
Terminal DEBUG output is distinct from Cypress driver logs running in the browser. If the issue occurs inside the browser during cypress open, open DevTools and enter this in its console:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutelocalStorage.debug = 'cypress*'Reload the page, then enable Verbose messages in the console. This exposes browser-side cypress:driver logs. The steps and namespace details are in Cypress’s troubleshooting guide.
Find screenshots, videos, and recorded-run evidence
- Manual screenshot: call
cy.screenshot()in eithercypress openorcypress run. - Failure screenshot:
cypress runcaptures these by default;cypress opendoes not automatically capture them. The default directory iscypress/screenshots. Configuration can change the directory or disable failure screenshots. - Video: Cypress can record a video for each spec during
cypress runwhen video recording is enabled. - Test Replay: for recorded Cypress Cloud runs, Test Replay lets you replay execution with debugging capability. It requires a recorded run and applicable Cloud access.
These are complementary evidence, not substitutes for inspecting the command sequence. See Capture screenshots and videos in Cypress and open mode.
Isolate slowdowns related to the Command Log
Cypress documents cases where the Command Log can contribute to slow tests or browser crashes. As a diagnostic experiment, disable it for a run:
CYPRESS_NO_COMMAND_LOG=1 npx cypress runThe CLI also supports --no-runner-ui to hide the full Runner UI during a run. When the Command Log is disabled, screenshots and videos will not include it, so use this as an isolation step rather than a routine logging setup. See the Cypress troubleshooting guide and CLI command reference.
Troubleshoot logs that are missing or unhelpful
- No terminal debug output: confirm the environment variable was set in the shell that launches Cypress and that the assignment syntax matches that shell. Check whether permissions affect the process.
- Too much output or a slower run: replace
DEBUG=cypress:*with the narrowest relevant namespace, then turn debugging off when finished. - Need details for a command’s input or result: use open mode, keep DevTools open, and click the corresponding Command Log entry.
- Browser driver issue, but no useful Node-side logs: enable
localStorage.debug = 'cypress*', reload, and show Verbose console messages. - Failure screenshot absent: automatic failure screenshots apply to
cypress run, not open mode. Check screenshot configuration and the configured output directory. - Command Log may be involved in a slowdown or crash: try
CYPRESS_NO_COMMAND_LOG=1or--no-runner-uito isolate the effect, accounting for the loss of the log in screenshots and videos.
Or skip the browser setup
If the problem is capturing a web page itself rather than debugging Cypress command execution, ScreenshotNeo offers a screenshot API and MCP server. A single GET request can return an image or PDF; see the API documentation.
Quick Recap
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 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 are not billed, and response headers identify the page verdict and billing status. Its MCP server lets AI agents use screenshot, page-info, and PDF-capture tools. The free plan includes 1,000 screenshots a month without a card; paid plans start at $5 for 3,000.
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.
