That statement says a lot, coming from someone who's spent effort in developing the ecosystem around TAP. It confirms the general feel of the thread, that some aspects are missing or can be improved, for it to be a full-fledged, scalable testing protocol.
When I discovered TAP, its simplicity was so refreshing. In the particular project where I learned about it, the implementation was a single file, a snippet really, included in the tests folder. No dependencies, with such a small interface. I was able to whip up my own tiny tester, and have used it (or similar ones in other languages) over the years.
In a way, I'm glad the protocol stayed small. There are many feature ideas in this thread, and some do look useful (or essential even) - but I find great value in the stability of the spec, it's kind of timeless.
That statement says a lot, coming from someone who's spent effort in developing the ecosystem around TAP. It confirms the general feel of the thread, that some aspects are missing or can be improved, for it to be a full-fledged, scalable testing protocol.
When I discovered TAP, its simplicity was so refreshing. In the particular project where I learned about it, the implementation was a single file, a snippet really, included in the tests folder. No dependencies, with such a small interface. I was able to whip up my own tiny tester, and have used it (or similar ones in other languages) over the years.
In a way, I'm glad the protocol stayed small. There are many feature ideas in this thread, and some do look useful (or essential even) - but I find great value in the stability of the spec, it's kind of timeless.