You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is related to the detekt testing framework and the hasLocationStrings custom assert.
After some investigation looks like the hasLocationStrings we're using in the tests is broken and is never asserting properly. Apparently the hasLocationStrings are always succeeding and a failure is never raised.
Expected Behavior
The hasLocationStrings assertion should fail if the provided location string is not correct.
This issue is related to the detekt testing framework and the
hasLocationStrings
custom assert.After some investigation looks like the
hasLocationStrings
we're using in the tests is broken and is never asserting properly. Apparently thehasLocationStrings
are always succeeding and a failure is never raised.Expected Behavior
The
hasLocationStrings
assertion should fail if the provided location string is not correct.Observed Behavior
The
hasLocationStrings
assertion never fails.Steps to Reproduce
I do have a branch where tests are supposed to be broken:
https://github.com/cortinico/detekt/tree/break-hasLocationString
Specifically in this commit: cortinico@7077bf3
Looks like all the tests passed:
https://github.com/cortinico/detekt/runs/149976114
Context
See comments in #1690
The text was updated successfully, but these errors were encountered: