So currently they don't, and that's why it fails.....
# kotlintest
d
So currently they don't, and that's why it fails... I think that's probably good for individual assertions, I think tests should be as explicit as possible the tester should spell out exactly what he/she's expecting and not rely on the implicit. But in the case of
should { }
, the
foo
is nullable, not the
bar
and to be able to make further assertions it must not be null, so I think it's different (since the very fact that the tester is requiring further assertions is assuming that the result will not be null), but a name that clearly expresses that might be better...?