Skip to content

Latest commit

 

History

History
56 lines (34 loc) · 2.96 KB

File metadata and controls

56 lines (34 loc) · 2.96 KB

Frequently asked questions

--env / tags isn't picked up

This might be because you're trying to specify -e / --env multiple times, but multiple values should be comma-separated.

I get fs_1.promises.rm is not a function

Upgrade your node version to at least v14.14.0.

I get spawn cucumber-json-formatter ENOENT

You need to install cucumber-json-formatter yourself, as per documentation.

Why is cypress-tags missing?

The cypress-tags executable has been removed and made redundant. Specs containing no matching scenarios are automatically filtered, provided that filterSpecs is set to true.

My JSON report isn't generated

You have likely stumbled upon a configuration caveat, see docs/configuration.md: Caveats / Debugging.

JSON reports aren't generated in open / interactive mode

JSON reports aren't typically generated in open / interactive mode. They rely on some events that aren't available in open-mode, at least not without experimentalInteractiveRunEvents: true. However, this experimental flag broke some time ago, ref. cypress-io/cypress#18955.

I get cypress_esbuild_preprocessor_1.createBundler is not a function

This can happen if you have a TypeScript Cypress configuration (IE. cypress.config.ts as opposed to cypress.config.js) similar to one of our examples and have a tsconfig.json without { "compilerOptions": { "esModuleInterop": true } }.

If you're really adamant about not using esModuleInterop: true, you can change

import createBundler from "@bahmutov/cypress-esbuild-preprocessor";

.. to

import * as createBundler from "@bahmutov/cypress-esbuild-preprocessor";

However, I recommend just using esModuleInterop: true if you don't fully understand the implications of disabling it.

I get cypress_esbuild_preprocessor_1.default is not a function

See answer above.