-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Rule request: quick_discouraged_focused_test #1905
Comments
ornithocoder
added a commit
to ornithocoder/personal-fork-swiftlint
that referenced
this issue
Oct 15, 2017
ornithocoder
added a commit
to ornithocoder/personal-fork-swiftlint
that referenced
this issue
Oct 15, 2017
ornithocoder
added a commit
to ornithocoder/personal-fork-swiftlint
that referenced
this issue
Oct 15, 2017
ornithocoder
added a commit
to ornithocoder/personal-fork-swiftlint
that referenced
this issue
Oct 15, 2017
ornithocoder
added a commit
to ornithocoder/personal-fork-swiftlint
that referenced
this issue
Oct 15, 2017
ornithocoder
added a commit
to ornithocoder/personal-fork-swiftlint
that referenced
this issue
Oct 15, 2017
Done in #1906. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's quite common - in large test suites - the usage of focused test (
fdescribe
,fcontext
, andfit
), especially when doing TDD.Focused test is a pretty handy feature, but not rarely do developers push code with focused test without realizing it :-(
This rule would trigger a warning for focused tests, to remind developers they have focused tests.
Non Triggering Examples
Triggering Examples
The text was updated successfully, but these errors were encountered: