Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gracefully handle unfound attributes #12

Open
Jameskmonger opened this issue Mar 31, 2016 · 0 comments
Open

Gracefully handle unfound attributes #12

Jameskmonger opened this issue Mar 31, 2016 · 0 comments

Comments

@Jameskmonger
Copy link

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
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant