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
The test suite I'm working with uses file locks on destructors to ensure things run synchronously. Having tests panic breaks that (unless we catch panics). Easiest way is to use all the .try_*() methods like .try_success() and .try_stderr().
However as far as I can tell there isn't a Result-returning way to do .assert(), which can panic, so filing this issue to ask whether we could have that.
The text was updated successfully, but these errors were encountered:
The test suite I'm working with uses file locks on destructors to ensure things run synchronously. Having tests panic breaks that (unless we catch panics). Easiest way is to use all the
.try_*()
methods like.try_success()
and.try_stderr()
.However as far as I can tell there isn't a Result-returning way to do
.assert()
, which can panic, so filing this issue to ask whether we could have that.The text was updated successfully, but these errors were encountered: