Error occurs when referencing the upper hierarchy with specPattern

Current behavior

I execute test specs in the hierarchy above the folder specified by “–project”. By updating Cypress v10, integrationFolder option was removed and replaced with specPattern option. When I replace integrationFolder option with specPattern option and execute test specs, below error is happened.

Error: EINVAL: invalid argument, mkdir 'C:\Users\<user>\AppData\Roaming\Cypress\cy\production\projects\project-ebb3941567b10beb6f33096d39c6ad57\bundles\D:\ProgramData\workspace\sample\test'

My project strucutre is separated with settings folder and test spcec folder. So, I execute cypress with “–project” option.

• My project structure

<Project>
  ├─Path
  │  └─to
  │     └─project
  │         ├─fixtures
  │         ├─support
  │         └─cypress.config.js
  └─test
      └─spec.cy.js

• Execute command

npx cypress open --project .\path\to\project

• cypress.config.js

const { defineConfig } = require("cypress");

module.exports = defineConfig({
  e2e: {
    specPattern: "../../../test/*.cy.js"
  }
});

Cypress 9.x with integrationFolder don’t happen this problem.

Desired behavior

Cypress can execute test specs in the hierarchy above the folder specified by “–project”

Test code to reproduce

• cypress.config.js

const { defineConfig } = require("cypress");

module.exports = defineConfig({
  e2e: {
    specPattern: "../../../test/*.cy.js"
  }
});

Cypress Version

10.0.2 (happens 10.0.0 and above)

Other

No response

[flotwig]

Definitely a regression in v10. However, I’d like to point out that this isn’t “best practice” to set up your Cypress tests like this. You can use a central package to manage the cypress version and use --project to point to a cypress.config.js per package.

[Sjeiti]

use a central package to manage

@flotwig Does this mean the Nx implementation of Cypress is not best practice? Were you referring to globs outside the cypress.config-directory or the use of a central package?