search

axross / tap-diff

:dancers: The most human-friendly TAP reporter.
MIT License
94 stars 26 forks source link

Gracefully handle unfound attributes #12

Open Jameskmonger opened 8 years ago

Jameskmonger commented 8 years ago

If there is no expected or actual attribute in the TAP details, they are displayed as undefined.

tap-heart undefined

I think that generally to comply with the TAP specification, if either expected and actual are not found in the YAML output, you should instead render the output directly as raw YAML.

Here is the output which causes the above screenshot:

# failing test
not ok 66 notEqual: [5]
  ---
    forbidden: 5
  ...