Geolocation error on final command of final test

cypress-io / github-action

GitHub Action for running Cypress end-to-end & component tests

https://on.cypress.io/guides/continuous-integration/github-actions

MIT License

1.35k stars 357 forks source link

Geolocation error on final command of final test #1195

Closed Fy50167 closed 2 months ago

Fy50167 commented 3 months ago

My applications has a dialog that opens up and covers all other elements if locations permissions are not enabled in the browser. Generally this doesn't interfere with my cypress tests whatsoever since we run our tests through Chrome instead of Electron, however in Github Actions (and only in actions, this doesn't occur in cypress locally) on the final action of the final test that gets ran (which is a click), the test fails because the dialog opens up and covers everything. I have no clue what could be causing this to occur since if locations weren't enabled I'm assuming the error would be occurring earlier or in any of the 5 tests that pass before, but for some reason it only shows up on the very last command that gets run.

MikeMcC399 commented 3 months ago

@Fy50167

The Cypress GitHub Action has no influence on individual steps in a set of tests, so it is very unlikely that there is a bug in the action which would cause the problem you are describing.

You may be able to get help from the Cypress technical community on Discord

(click on button)

You can find community members there with a broad base of experience which you can draw on.

jennifer-shehane commented 3 months ago

@Fy50167 Looks like this may be this issue: https://github.com/cypress-io/cypress/issues/2671 There's a workaround in there.

MikeMcC399 commented 3 months ago

@Fy50167

Please let us know if the link to https://github.com/cypress-io/cypress/issues/2671 was helpful to you

Fy50167 commented 3 months ago

@Fy50167

Please let us know if the link to Automatically accept geolocation permission / mock geolocation for tests cypress#2671 was helpful to you

Unfortunately not, basically every solution listed is outdated and deprecated at this point.

MikeMcC399 commented 3 months ago

@Fy50167

Unfortunately not, basically every solution listed is outdated and deprecated at this point.

Do you have a reproduction of this issue which you could share? I would suggest opening a new issue on https://github.com/cypress-io/cypress and using the template there to capture additional details, like version information.

MikeMcC399 commented 2 months ago

I suggest to close this issue since it cannot be solved by the Cypress GitHub Action.