4 ms·
Random: I found out recently that Ruby has no unified test output standard, and that every tool makes up its own o_O Not only this, but there is active resista
by peteretep 15y ago
Random: I found out recently that Ruby has no unified test output standard, and that every tool makes up its own o_O
Not only this, but there is active resistance to useing something like TAP.
- zaphar 15y agoI've always had a soft spot for TAP's output format. It just seems like it has potential for much better debuggability. The concept of a plan alone puts it above xUnit styles in my mind. That and the expectation that each assertion has a descriptive message just makes it's output seem easier to follow.
- pnathan 15y agoTAP is nice. I think it could use some extensions... but when I handrolled a test program a few years ago, I chose TAP. It... works.
- spitfire 15y agoWhat is TAP?
- jrockway 15y agoThe Test Anything Protocol: http://testanything.org/wiki/index.php/Main_Page http://testanything.org/wiki/index.php/Main_Page
- spitfire 15y agoOne of the frustrating parts of the technology industry is that it moves so damn fast, and people love acronyms. As a result, a new acronym every day. It looks like an interesting tool, I'll investigate it.
- telemachos 15y agoChristian Neukirchen (the creator of Rack, among other things) created knock[1], a TAP tool for Ruby. It doesn't seem to have developed much a following, though. [1] https://github.com/chneukirchen/knock https://github.com/chneukirchen/knock