You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TAP 14 spec allows for identifying a test as a "subtest"
TAP version 14
1..2
# Subtest: foo.tap
1..2
ok 1
ok 2 - this passed
ok 1 - foo.tap
# Subtest: bar.tap
ok 1 - object should be a Bar
not ok 2 - object.isBar should return true
---
found: false
wanted: true
at:
file: test/bar.ts
line: 43
column: 8
...
ok 3 - object can bar bears # TODO
1..3
not ok 2 - bar.tap
---
fail: 1
todo: 1
...
Is migrating to TAP 14 on the roadmap?
This would allow beautifiers to correctly indent subtests as TAP 13 has no mechanism for indicating the "level" of a test (everything is just flat comments).
The text was updated successfully, but these errors were encountered:
Yes, that sounds great. I have no idea how to go about doing that tho :-)
what would be ideal is an env var that sets the TAP version (explicit but unsupported versions should error), that defaults to 13 - then in a future semver-major we could change the default to 14.
TAP 14 spec allows for identifying a test as a "subtest"
Is migrating to TAP 14 on the roadmap?
This would allow beautifiers to correctly indent subtests as TAP 13 has no mechanism for indicating the "level" of a test (everything is just flat comments).
The text was updated successfully, but these errors were encountered: