A zero-spec result can mean two very different things depending on your workflow. Cypress 15.11.0 gives you a flag to handle it intentionally, whichever way you need.

Cypress's platform is a resource for developers and QA engineers, offering insights into end-to-end testing, test automation frameworks, and modern web application testing. Through articles, tutorials, and documentation, Cypress offers insights into writing and running automated tests for web applications. Developers can learn about Cypress's testing features, including real-time feedback, browser snapshots, and debugging tools, to ensure the quality and reliability of their web applications.

cypress

Cypress 15.11.0 introduces the `--pass-with-no-tests` CLI flag to handle CI pipeline failures caused by zero spec files being found. Previously, any run that matched no test files would exit with a non-zero code and break the build. The new flag allows Cypress to exit with code 0 in those cases, which is useful for workflows like dynamic spec filtering with cypress-grep or test quarantine setups where zero specs is an intentional and valid outcome. The post advises caution: teams should only use the flag when zero specs is genuinely expected, since a failing build can be a useful signal for misconfigured patterns. The release also adds React SSR hydration mismatch workarounds, Brotli compression support in the proxy, and metadata capture for additional CI providers in Cypress Cloud.

Fix Cypress CI failures caused by no spec files found

What causes "no spec files found" failures in Cypress?

Example: running Cypress with no specs in CI