Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation instructions only for legacy Cypress 9.x and lower #701

Closed
MikeMcC399 opened this issue Oct 3, 2023 · 1 comment · Fixed by #752
Closed

Installation instructions only for legacy Cypress 9.x and lower #701

MikeMcC399 opened this issue Oct 3, 2023 · 1 comment · Fixed by #752
Labels

Comments

@MikeMcC399
Copy link

MikeMcC399 commented Oct 3, 2023

Issue

The installation instructions in the README > Install section refer to:

Add to your cypress/support/index.js file

Register tasks in your cypress/plugins/index.js file

The above files are for Cypress legacy configurations with version 9.x and lower.

These files are also referred to in other parts of the README document.

Suggestion

  1. The installation section README > Install should be updated to cover installation on Cypress current configuration versions 10.x and later. These are already included on https://docs.cypress.io/guides/tooling/code-coverage#Install-the-plugin.

  2. If Cypress legacy configurations with version 9.x are still supported by the current version of @cypress/code-coverage then the old installation instructions could be left in, otherwise they should be removed and replaced by a note to the effect that 9.x and earlier are no longer supported.

  3. Update the remaining sections of the document accordingly.

Cypress 10.x migration guide

The Cypress 10 Migration Guide describes the relevant changes:

@cypress-app-bot
Copy link

🎉 This issue has been resolved in version 3.12.13 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants