TestAnything/Specification

Issues

• Test2 subtests not supported?

  #34 opened 2 years ago by exodist
  19

• A test running addendum?

  #42 opened 2 years ago by Leont
  1

• Interpreting TAP streams lacking version numbers

  #41 opened 2 years ago by isaacs
  13

• Formatting error under “YAML diagnostics” heading

  #44 opened 2 years ago by bigsmoke
  0

• What "shape" of data structure can properly hold the results of a parsed TAP log?

  #45 opened 2 years ago by ianfixes
  0

• "# time=..." directive

  #16 opened 10 years ago by isaacs
  8

• Add links to TAP14 producer and/or consumers reference implementations

  #32 opened 2 years ago by ligurio
  1

• Highlight innovations of TAP14 in the text of specification

  #33 opened 2 years ago by ligurio
  2

• Upgrade path from TAP13 to TAP14

  #13 opened 10 years ago by jonathanKingston
  4

• Error in sentence in the synopsis?

  #31 opened 2 years ago by rauschma
  1

• Extending TAP to define parameters controlling the TAP producers.

  #38 opened 2 years ago by 0xorial
  2

• Platform

  #36 opened 2 years ago by Jokerboss3
  3

• Gg

  #37 opened 2 years ago by Jokerboss3
  1

• Key

  #35 opened 2 years ago by Jokerboss3
  1

• Expected YAML output for multiple messages

  #30 opened 3 years ago by torarnv
  2

• Should a test be executed when skipped?

  #23 opened 3 years ago by Jameskmonger
  2

• Subtests Recap/Refresh

  #29 opened 3 years ago by isaacs
  7

• Encoding?

  #12 opened 3 years ago by Leont
  6

• whitespace before directive?

  #28 opened 3 years ago by isaacs
  6

• Hyphens between test number and description?

  #21 opened 10 years ago by riddochc
  5

• Repeated test point IDs

  #27 opened 3 years ago by isaacs
  10

• Test Point descriptions containing "#"

  #26 opened 3 years ago by isaacs
  7

• Exit code responsibility

  #22 opened 3 years ago by Jameskmonger
  5

• Standardise core functionality within the TAP YAML format.

  #9 opened 3 years ago by jonathanKingston
  18

• Pragmas

  #6 opened 3 years ago by Leont
  14

• Collaboration towards a formal specification and future governance

  #20 opened 3 years ago by isaacs
  4

• Standarize the notation of subtests in TAP

  #2 opened 10 years ago by kinow
  88

• Support diagnostics *before* the ok/not ok line

  #24 opened 8 years ago by cdleonard
  2

• New TAP should not care about order

  #14 opened 10 years ago by exodist
  8

• Ownership of specification?

  #17 opened 10 years ago by isaacs
  23

• Collaboration structure

  #19 opened 10 years ago by smikes
  4

• New features must not break existing consumers

  #18 opened 10 years ago by beatgammit
  4

• Concurrency should be supported.

  #15 opened 10 years ago by exodist
  12

• Be library and language agnostic

  #5 opened 10 years ago by jonathanKingston
  8

• Specify an extensible format within the YAML for agents to add further information

  #8 opened 10 years ago by jonathanKingston
  3

• Attach diagnostics to tests

  #11 opened 10 years ago by Leont
  9

• Public roadmap for each upcoming TAP specification version

  #10 opened 10 years ago by kinow
  14

• Agree upon a mime type

  #7 opened 10 years ago by jonathanKingston
  4

• Consider alternative transports/formats/markup for TAP

  #1 opened 10 years ago by jonathanKingston
  18

• Specify how consumers should handle parse errors

  #4 opened 10 years ago by jonathanKingston
  7

• Create test scripts for common consumers

  #3 opened 10 years ago by jonathanKingston
  0