You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When --spec option has glob [...] (even if escaped), cypress splits the argument at weird position, while it should be split by comma.
It is not only output text issue: specified spec files are actually not found by cypress even they are exists.
Desired behavior
No response
Test code to reproduce
Case 1: Split at middle of the filename
$ npx cypress run --spec 'cypress/integration/foo/bar/[baz]/test.ts,cypress/integration/foo/bar/[baz2]/test.ts,cypress/integration/foo3/bar/baz/test.ts,cypress/integration/foo4/bar/baz/foooooooooooooooo.ts'
Can't run because no spec files were found.We searched for specs matching these glob patterns: > /path/to/project/e2e/cypress/integration/foo/bar/[baz]/test.ts > /path/to/project/e2e/cypress/integration/foo/bar/[baz2]/test.ts > /path/to/project/e2e/cypress/integration/foo3/bar/baz/test.ts,cypress/integration/foo4/bar/baz/foooooo > /path/to/project/e2e/oooooooooo.ts
Case 2: Does not split at comma
$ npx cypress run --spec 'cypress/integration/foo/bar/baz/test.ts,cypress/integration/foo/bar/[baz2]/test.ts,cypress/integration/foo3/bar/baz/test.ts,cypress/integration/foo4/bar/baz/foooooooooooooooo.ts'
Can't run because no spec files were found.We searched for specs matching these glob patterns: > /path/to/project/e2e/cypress/integration/foo/bar/baz/test.ts,cypress/integration/foo/bar/[baz2]/test.ts > /path/to/project/e2e/cypress/integration/foo3/bar/baz/test.ts > /path/to/project/e2e/cypress/integration/foo4/bar/baz/foooooooooooooooo.ts
Case 3: Even when globs are escaped
$ npx cypress run --spec 'cypress/integration/foo/bar/\[baz\]/test.ts,cypress/integration/foo/bar/\[baz2\]/test.ts,cypress/integration/foo3/bar/baz/test.ts,cypress/integration/foo4/bar/baz/foooooooooooooooo.ts'
Can't run because no spec files were found.We searched for specs matching these glob patterns: > /path/to/project/e2e/cypress/integration/foo/bar/\[baz\]/test.ts > /path/to/project/e2e/cypress/integration/foo/bar/\[baz2\]/test.ts > /path/to/project/e2e/cypress/integration/foo3/bar/baz/test.ts,cypress/integration/foo4/bar/baz/foooooooo > /path/to/project/e2e/oooooooo.ts
Working as expected when no glob patterns are specified:
$ npx cypress run --spec 'cypress/integration/foo/bar/baz/test.ts,cypress/integration/foo/bar/baz2/test.ts,cypress/integration/foo3/bar/baz/test.ts,cypress/integration/foo4/bar/baz/foooooooooooooooo.ts'
Can't run because no spec files were found.We searched for specs matching these glob patterns: > /path/to/project/e2e/cypress/integration/foo/bar/baz/test.ts > /path/to/project/e2e/cypress/integration/foo/bar/baz2/test.ts > /path/to/project/e2e/cypress/integration/foo3/bar/baz/test.ts > /path/to/project/e2e/cypress/integration/foo4/bar/baz/foooooooooooooooo.ts
Cypress Version
9.5.2
Other
No response
The text was updated successfully, but these errors were encountered:
Current behavior
When --spec option has glob
[...]
(even if escaped), cypress splits the argument at weird position, while it should be split by comma.It is not only output text issue: specified spec files are actually not found by cypress even they are exists.
Desired behavior
No response
Test code to reproduce
Case 1: Split at middle of the filename
Case 2: Does not split at comma
Case 3: Even when globs are escaped
Working as expected when no glob patterns are specified:
Cypress Version
9.5.2
Other
No response
The text was updated successfully, but these errors were encountered: