-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fix eslint-plugin-khan tests so that they can be run using jest #1090
Conversation
🦋 Changeset detectedLatest commit: dc73c80 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
GeraldRequired Reviewers
Don't want to be involved in this pull request? Comment |
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.
Ahh nice - thanks for the fixes!
I love that we're able to use |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1090 +/- ##
=======================================
Coverage 99.85% 99.85%
=======================================
Files 97 97
Lines 1392 1392
Branches 351 351
=======================================
Hits 1390 1390
Misses 1 1
Partials 1 1 Continue to review full report in Codecov by Sentry.
|
Size Change: 0 B Total Size: 4.63 kB ℹ️ View Unchanged
|
{ | ||
code: `expect(promise).resolves.not.toBe(true);`, | ||
|
||
errors: [ | ||
{messageId: "asyncMatchers", data: {matchers: ["resolves"]}}, | ||
], | ||
output: "await expect(promise).resolves.not.toBe(true);", | ||
}, |
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.
This was a duplicated test case which jest doesn't like.
Thanks for the fix @kevinb-khan ! 🎉 |
Summary:
#1085 caused an issue where tests were only running for one of the eslint plugin rules. Thanks @beaesguerra for noticing this. This PR updates our testing setup so that we can use jest to run the eslint-plugin-khan tests instead of mocha. It also fixes a few failures that are due to changes in eslint and RuleTester's behaviour.
Issue: None
Test plan: