List of specs not supporting wildcards

[SebeFromGermany]

I'm having an issue with the following command:
$ SPEC="cypress\folder1\**\*.spec.ts, cypress\folder2\**\*.spec.ts" npx cypress run --env split=1,splitIndex1=1

The command is not working as expected. It seems to skip all files, stating that no files were found. I'm not sure if I'm doing something wrong or if it's not supported to use wildcards in the list of specs.

Additional information:

• Cypress version: 12.10.0
• Cypress-Split version: 1.20.1
• Operating System: Windows 10 22H2

Any help would be appreciated.

[jd-brennan]

I ran into this too. I'm not sure how it's supposed to work. Is the cyress arg -spec supposed to show up in the config object? Might be that config object value for spec is not a string, but an object with two strings.

[jd-brennan]

I ran into this too. I'm not sure how it's supposed to work. Is the cyress arg -spec supposed to show up in the config object? Might be that config object value for spec is not a string, but an object with two strings.

I fixed my issue by moving spec to the env:

cypress run --env 'spec=cypress/integration/local/**/*.js'

[bahmutov]

I have tested the SPEC wildcards in #260 and they work on Mac and Linux. You could try debugging it by running with DEBUG=cypress-split variable to see the debug output

[SebeFromGermany]

@bahmutov The issue appears to be related to the use of backslashes in the spec filter. When forward slashes are used, cypress-split functions correctly. This seems to be a problem unique to Windows. A potential solution could be to implement path.posix.resolve to ensure that the type of slashes used does not cause any issues.

cypress-split/src/parse-inputs.js

Line 106 in e166a56

return path.resolve(specFilename)

[bahmutov]

@SebeFromGermany if this is still a problem, do you mind opening a PR with a fix?