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
My opinion is that this is a bad and discouraged practice, since the final assert disguise any implicit type conversions. For example in the case when the SUT is changed like in the case of #190
I suggest preferring the type safe version for every assert statement during testing (even in the case of boolean assertion). For example, like below.
I think yes, at least I am unaware of any non-safe asserts in the code. For the record, they are quite tricky and time consuming to locate since in most of the case the test pass because the implicit conversions kick in. I.e. the problem is with the semantic of the test case, not the implementation.
Consider the following code chunk.
My opinion is that this is a bad and discouraged practice, since the final assert disguise any implicit type conversions. For example in the case when the SUT is changed like in the case of #190
I suggest preferring the type safe version for every assert statement during testing (even in the case of boolean assertion). For example, like below.
The text was updated successfully, but these errors were encountered: