tappy

tappy copied to clipboard

Support TAP14's SubtestDocument

1

[TAP 14](https://testanything.org/tap-version-14-specification.html) supports SubtestDocument, which effectively is the request for #14 - currently tappy will impose an error on any documents adhering TAP14 to with this new SubtestDocument: ```shell (,...

bowerscd

Now that TAP14 is official, it would assume if tappy supported it. There's a lot to do to make tappy compliant with version 14. * #122 is one example.

mblayman

when run on a directory the tappy cli tool expects all files in a directory to be tap files and will fail otherwise

2

This makes it more painful to use than needs be in the case where one has a single "reports" dir that contains files of many types (junit xml files, tap...

cj-timothy-sampson

The tracker was not previously added to the runner because the `__init__` methods between 2.6 and later versions were so different. Now that 2.6 is no longer supported it may...

mblayman

The current TAP streaming ability of the TAP consumer parses all the lines and then outputs results at the end. For long running test suites, this is undesirable behavior. The...

mblayman

The `tappy` consumer will add extra errors to the test report if the TAP stream does not conform to the spec. There should be an option to skip those checks....

mblayman

Explicitly log a TAP v13+ version number as the first line of output

4

In [TAP v13](https://testanything.org/tap-version-13-specification.html) and higher, the specification says the first line must be: ``` TAP version 13 ``` or similar. Some TAP consumers (notably Meson) emit warnings if this line...

smcv

updates: - [github.com/astral-sh/ruff-pre-commit: v0.11.2 → v0.14.9](https://github.com/astral-sh/ruff-pre-commit/compare/v0.11.2...v0.14.9)

pre-commit-ci[bot]

Improve support for YAML blocks: - Allowing passing raw_yaml_block to tracker when adding test result - Output YAML block in generated TAP file * [x] Is your name/identity in the...

codambro