Skip to content
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.

Add eslint no-exclusive-tests rule #893

Closed
slaweet opened this issue Oct 20, 2017 · 0 comments
Closed

Add eslint no-exclusive-tests rule #893

slaweet opened this issue Oct 20, 2017 · 0 comments
Assignees
@slaweet
Labels
*easy standards

Comments

@slaweet
Copy link
Contributor

slaweet commented Oct 20, 2017

Expected behaviour

Eslint should fail if we have exclusive tests like describe.only or it.only.

Actual behaviour

Currently we don't have this rule included.

Steps to reproduce

Try running npm run eslint while having a random exclusive test.
@slaweet slaweet self-assigned this Nov 20, 2017
@slaweet slaweet mentioned this issue Nov 20, 2017
Merged
1 task
slaweet added a commit that referenced this issue Nov 21, 2017
@slaweet
Merge pull request #993 from LiskHQ/893-add-eslint-no-exclusive-tests
260d1a4 
 Add eslint no-exclusive-tests rule - Closes #893
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@slaweet slaweet

Labels
*easy standards
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@slaweet