-
Notifications
You must be signed in to change notification settings - Fork 91
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: add linting rule for before/beforeEach just like the async test rule #151
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
cbd8cff
Feat: add linting rule for before/beforeEach just like the async rule…
Arcturus5404 aea3cef
Fix the unit test
Arcturus5404 cb6093d
Fix the unit test
Arcturus5404 fbc99a4
Update docs/rules/no-async-before.md
Arcturus5404 b0772e1
Update docs/rules/no-async-before.md
Arcturus5404 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
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,52 @@ | ||||||
# Prevent using async/await in Cypress test cases (no-async-tests) | ||||||
|
||||||
Cypress commands that return a promise may cause side effects in before/beforeEach hooks, possibly causing unexpected behavior. | ||||||
|
||||||
## Rule Details | ||||||
|
||||||
This rule disallows using `async` `before` and `beforeEach` functions. | ||||||
|
||||||
Examples of **incorrect** code for this rule: | ||||||
|
||||||
```js | ||||||
describe('my feature', () => { | ||||||
before('my test case', async () => { | ||||||
await cy.get('.myClass') | ||||||
// other operations | ||||||
}) | ||||||
}) | ||||||
``` | ||||||
|
||||||
```js | ||||||
describe('my feature', () => { | ||||||
before('my test case', async () => { | ||||||
cy | ||||||
.get('.myClass') | ||||||
.click() | ||||||
|
||||||
await someAsyncFunction() | ||||||
}) | ||||||
}) | ||||||
``` | ||||||
|
||||||
Examples of **correct** code for this rule: | ||||||
|
||||||
```js | ||||||
describe('my feature', () => { | ||||||
before('my test case', () => { | ||||||
cy.get('.myClass') | ||||||
// other operations | ||||||
}) | ||||||
}) | ||||||
|
||||||
``` | ||||||
|
||||||
## When Not To Use It | ||||||
|
||||||
If there are genuine use-cases for using `async/await` in your before then you may not want to include this rule (or at least demote it to a warning). | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
## Further Reading | ||||||
|
||||||
- [Commands Are Asynchronous](https://docs.cypress.io/guides/core-concepts/introduction-to-cypress.html#Commands-Are-Asynchronous) | ||||||
- [Commands Are Promises](https://docs.cypress.io/guides/core-concepts/introduction-to-cypress.html#Commands-Are-Promises) | ||||||
- [Commands Are Not Promises](https://docs.cypress.io/guides/core-concepts/introduction-to-cypress.html#Commands-Are-Not-Promises) |
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,47 @@ | ||
'use strict' | ||
|
||
module.exports = { | ||
meta: { | ||
docs: { | ||
description: 'Prevent using async/await in Cypress before methods', | ||
category: 'Possible Errors', | ||
recommended: true, | ||
}, | ||
messages: { | ||
unexpected: 'Avoid using async functions with Cypress before / beforeEach functions', | ||
}, | ||
}, | ||
|
||
create (context) { | ||
function isBeforeBlock (callExpressionNode) { | ||
const { type, name } = callExpressionNode.callee | ||
|
||
return type === 'Identifier' | ||
&& name === 'before' || name === 'beforeEach' | ||
} | ||
|
||
function isBeforeAsync (node) { | ||
return node.arguments | ||
&& node.arguments.length >= 2 | ||
&& node.arguments[1].async === true | ||
} | ||
|
||
return { | ||
Identifier (node) { | ||
if (node.name === 'cy' || node.name === 'Cypress') { | ||
const ancestors = context.getAncestors() | ||
const asyncTestBlocks = ancestors | ||
.filter((n) => n.type === 'CallExpression') | ||
.filter(isBeforeBlock) | ||
.filter(isBeforeAsync) | ||
|
||
if (asyncTestBlocks.length >= 1) { | ||
asyncTestBlocks.forEach((node) => { | ||
context.report({ node, messageId: 'unexpected' }) | ||
}) | ||
} | ||
} | ||
}, | ||
} | ||
}, | ||
} |
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,25 @@ | ||
'use strict' | ||
|
||
const rule = require('../../../lib/rules/no-async-before') | ||
const RuleTester = require('eslint').RuleTester | ||
|
||
const ruleTester = new RuleTester() | ||
|
||
const errors = [{ messageId: 'unexpected' }] | ||
// async functions are an ES2017 feature | ||
const parserOptions = { ecmaVersion: 8 } | ||
|
||
ruleTester.run('no-async-before', rule, { | ||
valid: [ | ||
{ code: 'before(\'a before case\', () => { cy.get(\'.someClass\'); })', parserOptions }, | ||
{ code: 'before(\'a before case\', async () => { await somethingAsync(); })', parserOptions }, | ||
{ code: 'async function nonTestFn () { return await somethingAsync(); }', parserOptions }, | ||
{ code: 'const nonTestArrowFn = async () => { await somethingAsync(); }', parserOptions }, | ||
], | ||
invalid: [ | ||
{ code: 'before(\'a test case\', async () => { cy.get(\'.someClass\'); })', parserOptions, errors }, | ||
{ code: 'beforeEach(\'a test case\', async () => { cy.get(\'.someClass\'); })', parserOptions, errors }, | ||
{ code: 'before(\'a test case\', async function () { cy.get(\'.someClass\'); })', parserOptions, errors }, | ||
{ code: 'beforeEach(\'a test case\', async function () { cy.get(\'.someClass\'); })', parserOptions, errors }, | ||
], | ||
}) |
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.
Does this issue also occur in after/afterEach lifecycle hooks? Maybe
no-async-hooks
might be a better rule, if this is the case.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 guess so, but I am not sure they will cause a problem. It might has the same potential to break your testcase. Should the new hook rule also include the test rule? one to rule them all?
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 do know that in before and beforeEach the async code might actually break the test, because of the dependency. But there might not be a problem as such in the after because of race conditions