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 →From your Cypress project root, run npx cypress run. Cypress runs the configured suite to completion, headlessly by default. “All” means every spec discovered for the project and its active testing type—not every test file anywhere on your computer.
Run the full configured suite
Open a terminal in the project root—the directory containing the Cypress project—and run:
As an Amazon Associate I earn from qualifying purchases.
npx cypress runThis is the standard command-line way to run Cypress tests to completion. Cypress uses the project’s configuration to discover eligible specs, then runs them on the current machine. The run is headless by default.
Equivalent package-manager forms include:
yarn cypress runpnpm cypress runbunx cypress run
Do not add --spec if you want the full configured suite: that option narrows which specs Cypress considers.
What counts as “all” specs?
Cypress discovers specs according to the project configuration and testing type. A file must match the applicable specPattern; files matched by excludeSpecPattern are left out. Cypress treats End-to-End and Component Testing as separate testing types, each with its own configuration.
So npx cypress run runs all specs Cypress discovers for the project and active testing type. It does not override exclusions or make an out-of-pattern file eligible.
Run a subset when you need one
For a focused run, pass a file path, a comma-separated set of paths, or a glob to --spec. Quote globs so the shell passes the pattern to Cypress:
Free tools Windows power users keep installed
One-click scans. No signup required.
npx cypress run --spec "cypress/e2e/login.cy.js"
npx cypress run --spec "cypress/e2e/login/**/*"The selection still intersects with specPattern. Passing a path explicitly will not cause Cypress to run a file that falls outside the configured pattern.
Choose between a local run, the Runner UI, and parallel CI
| Approach | Where it runs | What it runs | Key trade-off or requirement |
|---|---|---|---|
npx cypress run |
One local or CI machine | All discovered specs unless configuration or command filtering narrows discovery | Simple whole-suite invocation; execution is on that machine. |
npx cypress run --spec ... |
One machine | Only the selected subset, intersected with specPattern |
Useful for focused checks, not a full-suite run. |
npx cypress run --record --parallel |
Multiple CI machines coordinated through Cypress Cloud | The recorded suite can be distributed across machines | Requires recording and multiple CI machines configured with the provider; whole spec files are distributed and their order is not guaranteed. |
| Runner UI experimental Run All Specs | Cypress desktop Runner | Sequential multi-spec UI workflow | Separate experimental option, disabled by default; unnecessary for the ordinary CLI run. |
When CI needs the suite sooner
For distributed execution, Cypress documents npx cypress run --record --parallel. Parallelization is a separate recorded CI workflow: configure multiple CI machines with the provider, and Cypress distributes whole spec files among them. A single long-running spec can become a bottleneck because the unit of distribution is the spec file.
Cypress’s performance guidance illustrates a Kitchen Sink run changing from 1:51 on one machine to 59 seconds on two machines. That is an example for that project and setup, not a general speed guarantee; actual results depend on the suite and infrastructure.
Why specs may be missing
- Check the working directory. Run the command from the intended project root, or specify the project with Cypress’s
--projectoption. - Inspect
specPattern. Check the applicable setting incypress.config.*. A path supplied through--specmust still match the configured pattern. - Check
excludeSpecPattern. Matching files are removed from discovery even if they otherwise appear eligible. - Remove inherited filtering. Look in package scripts and CI commands for a
--specargument that restricts the run. - Confirm the testing type. Determine whether the project is running E2E or Component Testing and check that type’s configuration.
Keep a large suite manageable
Running all specs in one CLI invocation does not require putting all tests into one spec file. Cypress has fixed browser, support-file, and application reload overhead for each spec, so spec organization involves a trade-off: very small files can add per-spec overhead, while one unusually large file can undermine parallel balance and test isolation. Organize specs around reliable isolation and maintainability, and use distributed CI when the full suite’s completion time is a problem.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Or skip the browser setup
If your goal is to capture a website screenshot rather than execute Cypress assertions, ScreenshotNeo is a separate screenshot API and MCP server—not a Cypress test runner. For a screenshot, one GET request can return an image or PDF:
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 documentation for parameters and formats. It can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; responses identify 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 with no card; paid plans start at $5 for 3,000 shots.
Sign up for the free plan to try 1,000 screenshots a month with no card.
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.
