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
We've had a few test failures recently that have resulted in exception traces, but none of the usual Midje failure messages. That makes it a bit hard to know which fact the error was in.
For example:
(fact "you never see this message" (/ 1 0))
results in a stack trace in your terminal, but you never see the "you never see this message" message. That makes it a little bit harder to read.
This is important for us because we do a bit of preparation in a let form before the actual assertions. And if there are any errors in the let block, you never see which form the error was in...
We've had a few test failures recently that have resulted in exception traces, but none of the usual Midje failure messages. That makes it a bit hard to know which fact the error was in.
For example:
results in a stack trace in your terminal, but you never see the "you never see this message" message. That makes it a little bit harder to read.
This is important for us because we do a bit of preparation in a let form before the actual assertions. And if there are any errors in the let block, you never see which form the error was in...
The text was updated successfully, but these errors were encountered: