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
feat(rules): add no-test-callback
rule
#179
Merged
Merged
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
a25ce2d
feat(rules): add `no-test-callback` rule
SimenB 463a671
chore: handle async functions as well
SimenB 2ac472c
refactor: cleanup
SimenB 421fa8b
chore: update docs/rules/no-test-callback.md
ranyitz 0a2d46e
chore: fix bug when argument is not a function expression
SimenB 2049bf8
chore: remove redundant test
macklinu File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,76 @@ | ||
# Avoid using a callback in asynchronous tests (no-test-callback) | ||
|
||
Jest allows you to pass a callback to test definitions, typically called `done`, | ||
that is later invoked to indicate that the asynchronous test is complete. | ||
|
||
However, that means that if your test throws (e.g. because of a failing | ||
assertion), `done` will never be called unless you manually use `try-catch`. | ||
|
||
```js | ||
test('some test', done => { | ||
expect(false).toBe(true); | ||
done(); | ||
}); | ||
``` | ||
|
||
The test above will time out instead of failing the assertions, since `done` is | ||
never called. | ||
|
||
Correct way of doing the same thing is to wrap it in `try-catch`. | ||
|
||
```js | ||
test('some test', done => { | ||
try { | ||
expect(false).toBe(true); | ||
done(); | ||
} catch (e) { | ||
done(e); | ||
} | ||
}); | ||
``` | ||
|
||
However, Jest supports a second way of having asynchronous tests - using | ||
promises. | ||
|
||
```js | ||
test('some test', () => { | ||
return new Promise(done => { | ||
expect(false).toBe(true); | ||
done(); | ||
}); | ||
}); | ||
``` | ||
|
||
Even though `done` is never called here, the Promise will still reject, and Jest | ||
will report the assertion error correctly. | ||
|
||
## Rule details | ||
|
||
This rule triggers a warning if you have a `done` callback in your test | ||
SimenB marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
The following patterns are considered warnings: | ||
|
||
```js | ||
test('myFunction()', done => { | ||
// ... | ||
}); | ||
|
||
test('myFunction()', function(done) { | ||
// ... | ||
}); | ||
``` | ||
|
||
The following patterns are not considered warnings: | ||
|
||
```js | ||
test('myFunction()', () => { | ||
expect(myFunction()).toBeTruthy(); | ||
}); | ||
|
||
test('myFunction()', () => { | ||
return new Promise(done => { | ||
expect(myFunction()).toBeTruthy(); | ||
done(); | ||
}); | ||
}); | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,90 @@ | ||
'use strict'; | ||
|
||
const RuleTester = require('eslint').RuleTester; | ||
const rule = require('../no-test-callback'); | ||
|
||
const ruleTester = new RuleTester({ | ||
parserOptions: { | ||
ecmaVersion: 8, | ||
}, | ||
}); | ||
|
||
ruleTester.run('no-test-callback', rule, { | ||
valid: [ | ||
'test("something", () => {})', | ||
'test("something", function() {})', | ||
'test("something", function () {})', | ||
SimenB marked this conversation as resolved.
Show resolved
Hide resolved
|
||
], | ||
invalid: [ | ||
{ | ||
code: 'test("something", done => {done();})', | ||
errors: [ | ||
{ | ||
message: 'Illegal usage of test callback', | ||
line: 1, | ||
column: 19, | ||
}, | ||
], | ||
output: | ||
'test("something", () => {return new Promise(done => {done();})})', | ||
}, | ||
{ | ||
code: 'test("something", (done) => {done();})', | ||
errors: [ | ||
{ | ||
message: 'Illegal usage of test callback', | ||
line: 1, | ||
column: 20, | ||
}, | ||
], | ||
output: | ||
'test("something", () => {return new Promise((done) => {done();})})', | ||
}, | ||
{ | ||
code: 'test("something", done => done())', | ||
errors: [ | ||
{ | ||
message: 'Illegal usage of test callback', | ||
line: 1, | ||
column: 19, | ||
}, | ||
], | ||
output: 'test("something", () => new Promise(done => done()))', | ||
}, | ||
{ | ||
code: 'test("something", (done) => done())', | ||
errors: [ | ||
{ | ||
message: 'Illegal usage of test callback', | ||
line: 1, | ||
column: 20, | ||
}, | ||
], | ||
output: 'test("something", () => new Promise((done) => done()))', | ||
}, | ||
{ | ||
code: 'test("something", function(done) {done();})', | ||
errors: [ | ||
{ | ||
message: 'Illegal usage of test callback', | ||
line: 1, | ||
column: 28, | ||
}, | ||
], | ||
output: | ||
'test("something", function() {return new Promise((done) => {done();})})', | ||
}, | ||
{ | ||
code: 'test("something", function (done) {done();})', | ||
errors: [ | ||
{ | ||
message: 'Illegal usage of test callback', | ||
line: 1, | ||
column: 29, | ||
}, | ||
], | ||
output: | ||
'test("something", function () {return new Promise((done) => {done();})})', | ||
}, | ||
], | ||
}); |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,75 @@ | ||
'use strict'; | ||
|
||
const getDocsUrl = require('./util').getDocsUrl; | ||
const isTestCase = require('./util').isTestCase; | ||
|
||
module.exports = { | ||
meta: { | ||
docs: { | ||
url: getDocsUrl(__filename), | ||
}, | ||
fixable: 'code', | ||
}, | ||
create(context) { | ||
return { | ||
CallExpression(node) { | ||
if (!isTestCase(node) || node.arguments.length !== 2) { | ||
return; | ||
} | ||
|
||
const callback = node.arguments[1]; | ||
|
||
if (callback.params.length === 1) { | ||
const argument = callback.params[0]; | ||
context.report({ | ||
node: argument, | ||
message: 'Illegal usage of test callback', | ||
fix(fixer) { | ||
const sourceCode = context.getSourceCode(); | ||
const body = callback.body; | ||
const firstBodyToken = sourceCode.getFirstToken(body); | ||
const lastBodyToken = sourceCode.getLastToken(body); | ||
const tokenBeforeArgument = sourceCode.getTokenBefore(argument); | ||
const tokenAfterArgument = sourceCode.getTokenAfter(argument); | ||
const argumentInParens = | ||
tokenBeforeArgument.value === '(' && | ||
tokenAfterArgument.value === ')'; | ||
|
||
let argumentFix = fixer.replaceText(argument, '()'); | ||
|
||
if (argumentInParens) { | ||
argumentFix = fixer.remove(argument); | ||
} | ||
|
||
let newCallback = argument.name; | ||
|
||
if (argumentInParens) { | ||
newCallback = `(${newCallback})`; | ||
} | ||
|
||
if (body.type === 'BlockStatement') { | ||
return [ | ||
argumentFix, | ||
fixer.insertTextAfter( | ||
firstBodyToken, | ||
`return new Promise(${newCallback} => {` | ||
), | ||
fixer.insertTextAfter(lastBodyToken, ')}'), | ||
]; | ||
} else { | ||
return [ | ||
argumentFix, | ||
fixer.insertTextBefore( | ||
firstBodyToken, | ||
`new Promise(${newCallback} => ` | ||
), | ||
fixer.insertTextAfter(lastBodyToken, ')'), | ||
]; | ||
} | ||
}, | ||
}); | ||
} | ||
}, | ||
}; | ||
}, | ||
}; |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think wrapping this code in a Promise as a fixer is a good first step and a consistent way to wrap code in the "return a Promise" paradigm. Do we also want to document using
.resolves
,.rejects
or returning a Promise / await statement as other suggested alternatives?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.
The thinking is that returning a promise is a safe change, as it will always work (I think?). Messing with the body of the tests are both way harder and more brittle. The current solution also makes no assumptions about assertions.
Regarding
resolve
andrejects
, I actually want to remove them from Jest and ask people to useasync-await
. That's a whole other can of worms, though 🙂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.
oh, I now understood that you meant the docs... I thought you talked about the fixer, sorry!
Yeah, we should definitely include some prose about using at least
async-wait
over returning the promise (async functions returns promises implicitly, so it's almost always a better idea anyways). Mentioningresolves
andrejects
(especiallyrejects
asresolves
i better handled byawait
) is probably a good idea as well.Would you mind sending a PR for it? 🙏
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.
@SimenB rejects is very useful to avoid using logic in try/catch blocks (like
.toThrow
but for async functions), so I would keep it (andresolves
for consistency) unless we come up with an equally good alternative.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.
Yeah, for sure.
What I want is same as ava (which returns the error from
t.throws
, but I'm not sure if that makes sense forexpect
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.
I just saw that ava has
throwsAsync
for that :DThere 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.
Ah, new in v1, it was just
throws
before. But yeah, I like that pattern. Doesn't fit intoexpect
, though