-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
feat(rule-tester): add support for snapshot testing rules #6994
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
Conversation
Thanks for the PR, @bradzacher! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
d7b97b4
to
ebc8745
Compare
Lots of merge conflicts and this is taking up space in the PR queue. I'm going to close this old draft just to keep the queue small. |
PR Checklist
Overview
This PR adds support for snapshot testing rules using a custom, framework agnostic snapshot setup.
The snapshot emits two files for each
.run
call - a markdown file which is the human-readable results of the test, and a binary file which is a compressed json blob containing the machine-readable snapshot information.I've done a test migration of our codebase here: https://github.com/typescript-eslint/typescript-eslint/tree/v6-rule-tester-snapshots-migrate-codebase
TODO:
filenamify
to ensure test names are valid filenames