Module API: cypress.run is unable to pick a specific test from within the integration folder

[borecz]

Cypress 6.2.1

Simple setup:

cypress.run({ spec: 'gtm/osp/track-ecommerce.events.spec.ts', configFile: 'cypress/config/configFiles/cypress-mobile.json' })

or
cypress.open({ configFile: 'cypress/config/configFiles/cypress-mobile.json' })

When I use cypress.open it correctly finds all the spec files (screenshot)

looking for this specific spec

[borecz]

any updates on this?

[bahmutov]

The way --spec CLI parameter and cypress.run({ spec: ... }) value work is different from what you select in the Cypress Desktop GUI search box.

• inside the search box we already use the Cypress integration folder setting and ignore test files pattern to show just the specs. Thus we do not show the typical "cypress/integration" folder
• when using --spec CLI parameter you typically are in the terminal at the root of the project. For example let's say we are in the folder ~/git/cypress-test-tiny and want to run a spec. The specs are in the folder cypress/integration/ui folder. Our files:

$ ls -R cypress/integration
ui

cypress/integration/ui:
spec.js

So you are typing the command, and it makes sense to use the shell's path to the spec file - this way I can type the spec filename quickly

spec-cli.mp4

Even if you are outside the Cypress folder, you can use the relative path from the current path this way. For example, if I am in ~/git folder and my project is in ~/git/cypress-test-tiny

$ ./cypress-test-tiny/node_modules/.bin/cypress run \
  --project ~/git/cypress-test-tiny \
  --spec ./cypress-test-tiny/cypress/integration/ui/spec.js 

The same thing happens with cypress.run({ spec: ... }) option. You need to use the relative path from the current folder. Some code editors even help you by showing the relative path popups, for example like my VSCode here

spec-option.mp4

Finally, I will keep this ticket open:

• I want to clarify this in our documentation
• it would be super helpful to show the current folder in the error message to make the error understandable and remove the confusion

[cypress-bot]

The code for this is done in cypress-io/cypress#14810, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 6.4.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v6.4.0, please open a new issue.