Skip to content

Conversation

@lo1tuma
Copy link
Owner

@lo1tuma lo1tuma commented Jul 8, 2019

There was one call of astUtils.isDescribe which has been called without the second parameter which caused the function to accept undefined as a valid alias for suite function names. Additionally there are cases where we don’t get a node name for CallExpressions (e.g. foo()()). So in such cases the extracted node name is undefined and isDescribe will return true due to the above mentioned
bug.

Fixes: #172

There was one call of `astUtils.isDescribe` which has been called
without the second parameter which caused the function to accept
`undefined` as a valid alias for suite function names. Additionally
there are cases where we don’t get a node name for `CallExpressions`
(e.g. `foo()()`). So in such cases the extracted node name is
`undefined` and `isDescribe` will return true due to the above mentioned
bug.

Fixes: #172
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

no-setup-in-describe aggressively pops its nesting

2 participants