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

[cjcrandall]

#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:

• cy.pause
• xdescribe/xit/.skip
• .only (Again, see Suggestion: add rule that prevents focused tests #57)
• cy.debug

[distante]

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

[cjcrandall]

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

[jcupps]

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]

• This is partially implemented in PR feat: add rule no-debug #216