Skip to content
This repository was archived by the owner on Oct 25, 2025. It is now read-only.
This repository was archived by the owner on Oct 25, 2025. It is now read-only.

Gracefully handle unfound attributes #12

Description

@Jameskmonger

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
  ...

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions