This is redundant with the information already available in
in the TestEnd event data.
We don't know of any testing frameworks that support flipping
the "todo" status on a per-assertion basis, nor does that
seem likely in the future as "Todo test" is defined as a test
with one or more expected failures.
Presence of this in the spec was a barrier to entry as it means
common assertion exception objects would require being cloned,
mutated, or otherwise mapped to set accordingly.
This is redundant with the information already available in in the TestEnd event data.
We don't know of any testing frameworks that support flipping the "todo" status on a per-assertion basis, nor does that seem likely in the future as "Todo test" is defined as a test with one or more expected failures.
Presence of this in the spec was a barrier to entry as it means common assertion exception objects would require being cloned, mutated, or otherwise mapped to set accordingly.
Fixes https://github.com/js-reporters/js-reporters/issues/105.