Skip to content

Expected YAML output for multiple messages #30

@torarnv

Description

@torarnv

The current spec describes a case for reporting messages via the YAML format:

TAP version 13
1..N
ok 1 Description # Directive
# Diagnostic
  ---
  message: 'Failure message'
  severity: fail
  data:
    got:
      - 1
      - 3
      - 2
    expect:
      - 1
      - 2
      - 3
  ...
ok 47 Description
ok 48 Description

What is the expected output when multiple messages are emitted?

  ---
    -
      message: 'Debug message'
      severity: debug
    -
      message: 'Warning message'
      severity: warning
  ...

This seems to be somewhat supported by the old archived spec, but breaks the assumption that the root namespace is a hash?

Do any producers or consumers today support this use-case in any way?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions