4 ms·

TAP is something that I invested a lot of time years ago, but nowadays I rarely have time to maintain any project, or contribute to the project (which is active

by kinow 6y ago

TAP is something that I invested a lot of time years ago, but nowadays I rarely have time to maintain any project, or contribute to the project (which is active on GitHub now https://github.com/testanything https://github.com/testanything, but before we had only a Wiki that would be offline and be restored from some backup a few times :) This is what I ended up being involved with: - Joined the mailing lists, and updated the Wiki. Eventually joined the new GitHub org - Created tap4j, using an existing implementation as reference (contacted the author, who helped with some questions too) https://github.com/tupilabs/tap4j https://github.com/tupilabs/tap4j - Created instanttap to validate the TAP streams - http://instanttap.appspot.com/ http://instanttap.appspot.com/ (surprised it's still working) - Created Jenkins TAP Plugin - Updated Jenkins TestLink Plugin to support TAP - Wrote a quick producer for GoogleTest https://github.com/kinow/gtest-tap-listener https://github.com/kinow/gtest-tap-listener - And wrote a few articles and presented the solution and/or TAP in conferences - And created the reddit r/testanythingprotocol subreddit to collect links I found about TAP IMO, TAP was going in the right direction. If it had been adopted by Python or JUnit, it would be much more popular now.

zdw 6y ago
Thank you for your work around TAP. I've used a few of the mentioned tools in my work, and really appreciate it.
lioeters 6y ago
> TAP was going in the right direction. 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.

by kinow 6y ago

zdw 6y ago

Thank you for your work around TAP. I've used a few of the mentioned tools in my work, and really appreciate it.

lioeters 6y ago

> TAP was going in the right direction. 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.