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
It can be hard to figure out where in a test case assertions are failing. For example if the test case has multiple call sites of a helper function that might fail it's impossible to figure out which call site is raising the HUnitFailure, because only the lower most SrcLoc of the callstack is shown.
I propose to always include the full stack trace in HUniFailure.
Without a full stackrace you can be lost:
Tests
Auth
LoginId parser: valid email: FAIL
test/unit/Test/Wire/API/User/Auth.hs:34:
Some assertion failed. Try to find me!
In contrast:
Tests
Auth
LoginId parser: valid email: FAIL
Error message: Some assertion failed. Try to find me!
CallStack (from HasCallStack):
assertFailure, called at test/unit/Test/Wire/API/User/Auth.hs:52:11 in main:Test.Wire.API.User.Auth
helper2, called at test/unit/Test/Wire/API/User/Auth.hs:49:10 in main:Test.Wire.API.User.Auth
helper, called at test/unit/Test/Wire/API/User/Auth.hs:34:3 in main:Test.Wire.API.User.Auth
The text was updated successfully, but these errors were encountered:
It can be hard to figure out where in a test case assertions are failing. For example if the test case has multiple call sites of a helper function that might fail it's impossible to figure out which call site is raising the HUnitFailure, because only the lower most SrcLoc of the callstack is shown.
I propose to always include the full stack trace in HUniFailure.
Without a full stackrace you can be lost:
In contrast:
The text was updated successfully, but these errors were encountered: