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

Suggestion: Add rule(s) to disallow debugging-related Cypress calls #74

Open
cjcrandall opened this issue Feb 3, 2021 · 4 comments
Open

Comments

@cjcrandall
Copy link

#57 already covers .only, but I think it would be valuable to either have a single rule, or individual rules, to cover other Cypress calls that are usually just for debugging and we don't want to accidentally commit to source control, including:

@distante
Copy link

I am really interested in this also! I see my self commiting .debug() and .pause() calls all the time :(

@cjcrandall
Copy link
Author

@distante it looks like a rule was added for .pause(). Still looking forward to the others.

@jcupps
Copy link

jcupps commented Mar 2, 2022

Hi, it looks like chained .pause() calls are not detected by this rule, which is confirmed in the docs:

Valid:

// only the parent cy.pause command is detected
cy.get('selector').pause();

Is there any particular reason for that, or has it just not been implemented yet? Thanks

@MikeMcC399
Copy link
Collaborator

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

No branches or pull requests

4 participants