I have the weirdest exception when running a unit ...
# arrow
n
I have the weirdest exception when running a unit test involving an either