Closed pahaeanx closed 9 months ago
Thank you for filing this bug. And awesome minimally reproducible example!
I'll investigate this sometime this week and fix, my guess is I'm not setting the field and it's defaulting to false.
v0.4.2 is released with this fix.
Thank you for reporting this, great catch!
Describe the bug After upgrading from
0.3.x
to0.4.1
I noticed that all my tests were failing, or at least it looked like it as I use thejson
output and decide based on a testssuccessful
field.With
0.4.x
it seems that this field is alwaysfalse
, even for tests that succeeded.How To Reproduce
Expected Behavior I'd expect successful tests to have their
successful
field to betrue
as was the case before0.4.x
.Actual Behavior See above. Seems the
successful
field is always set tofalse
and does not accurately reflect if a test has actually failed or not.Environment: