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
In my opinion, the following should be plenty enough:
eventually {
assert(condition)
true
}
No need for assertThis, assertThat, assertWhatever. No need for eventuallyThis, eventuallyThat, eventuallyWhatever. If you seek the convenience of such this that whatever, you should employ ScalaTest instead, not uTest.
@frgomes Thanks for the friendly contribution. My point is that I don't think it should be necessary to add a manual true after the assert. I would have expected my first code snippet to compile.
@NeQuissimus :: I certainly understand your point. My point is that uTest should not be polluted with this, that, whatever just because API X has a certain function or syntax construct which happens to not look nice or convenient. You may have a myriad of circumstances where something may not look nice or convenient and, if we extend uTest everytime something does not look nice or convenient, uTest will soon look like ScalaTest.
Using a combination of
eventually
andassertMatch
is currently rather inconvenient.assertMatch
returnsUnit
while eventually expectsBoolean
.So the following piece of code does not compile
while this does but only with a manual
true
as a workaround.Maybe an
eventually
that only cares about match errors or a neweventuallyMatch
could be added?The text was updated successfully, but these errors were encountered: