Confirm this plugin works with wildcard spec parameter

[bahmutov]

- name: Run bonus tests 🧪
  # https://github.com/cypress-io/github-action
  uses: cypress-io/github-action@v4
  with:
    spec: 'cypress/integration/bonus*.js'
  env:
    SPLIT: ${{ strategy.job-total }}
    SPLIT_INDEX: ${{ strategy.job-index }}

[dannyskoog]

Hi @bahmutov. I can confirm that this does not work. In my case my step looks like this:

    - name: Cypress run
      uses: cypress-io/github-action@v5
      with:
        install: false
        start: npx serve -l 8080
        wait-on: http://localhost:8080
        browser: chrome
        spec: cypress/e2e/staging/**/*.spec.ts
      env:
        SPLIT: ${{ strategy.job-total }}
        SPLIT_INDEX: ${{ strategy.job-index }}
        SERVICE_ACCOUNT: ${{ secrets.FIREBASE_ADMIN_SA_STAGE }}
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

But specs outside of the staging folder where ran anyway

[dannyskoog]

What did work, though, was using the config.specPattern parameter, i.e:

    - name: Cypress run
      uses: cypress-io/github-action@v5
      with:
        install: false
        start: npx serve -l 8080
        wait-on: http://localhost:8080
        browser: chrome
        config: specPattern=cypress/e2e/staging/**/*.spec.ts
      env:
        SPLIT: ${{ strategy.job-total }}
        SPLIT_INDEX: ${{ strategy.job-index }}
        SERVICE_ACCOUNT: ${{ secrets.FIREBASE_ADMIN_SA_STAGE }}
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

[bahmutov]

Yup, Cypress does not pass spec CLI argument anywhere, thus this plugin has no idea what to do, there is an issue I opened cypress-io/cypress#26032

I think for now I will work around it by asking the to pass the spec argument via env variable too, something like

    - name: Cypress run
      uses: cypress-io/github-action@v5
      with:
        install: false
        start: npx serve -l 8080
        wait-on: http://localhost:8080
        browser: chrome
        spec: cypress/e2e/staging/**/*.spec.ts
      env:
        SPLIT: ${{ strategy.job-total }}
        SPLIT_INDEX: ${{ strategy.job-index }}
        SPLIT_SPECS: cypress/e2e/staging/**/*.spec.ts

[dannyskoog]

I understand.

Yes, that could be reasonable. In my case (as seen above) I went with passing config.specPattern (which allowed me to just specify my pattern once) to the action since I noticed that your plugin had access to and was using it

[karfau]

What is the current status of this?
I tried the suggested things but nothing worked.
I'm still on cypress v9.1.1 which is most likely the reason that the specPattern config option is not accepted by cypress.
Docs are hard to find for the old version, so what are my options?
Would it help to modify the testFiles property of the config object to fit my spec pattern before passing it to the cypress=split plugin?
It seems to be a string (from the config file) when it is passed in and a list of files when it is returned. But i tried to use the spec pattern there without success...