-
Notifications
You must be signed in to change notification settings - Fork 29
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
chore: add eslint-plugin-playwright
rules for e2e tests and fix errors
#2680
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
eslint-plugin-playwright
rule for e2e tests and fix errorseslint-plugin-playwright
rules for e2e tests and fix errors
eslint-plugin-playwright
rules for e2e tests and fix errorseslint-plugin-playwright
rules for e2e tests and fix errors
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great find, love to see more automated linting
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for adding this!
* fix errors related to playwright/valid-describe-callback rule
f28534f
to
feb922f
Compare
None blocking comment: When running |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this addition!! 🙌
Description
This prs adds the
eslint-plugin-playwright
eslint rule with the recommended rules applied.There are 110 new warnings reported, most of which are either:
Avoid having conditionals in tests (playwright/no-conditional-in-test)
Test has no assertions (playwright/expect-expect)
We could:
I think these are good warnings to have though so I'd recommend either option 1. or 2.
How to Test
async
to a describe block callbackyarn lint
and/or within the editorChecklist
- [ ] I have added before and after screenshots for UI changes- [ ] I have added JSON response output for API changes- [ ] I have added steps to reproduce and test for bug fixes in the description- [ ] I have commented on my code, particularly in hard-to-understand areas- [ ] I have added tests that prove my fix is effective or that my feature works