Rodent of Unusual Size wrote: > > one solution to this one would be to a) have guidelines about the > test descriptions, such as > > ok($result eq $expected, "f(x): expected '$expected', got '$result'"); > > so that what was being attempted is clear
better still, if there was something like % t/TEST -whatis t/foo.t t/foo.t:1.....Test f(12) == 13 t/foo.t:2.....Test f(13) == 11 t/foo.t:3.....Test f(0) == pi in other words, a way for scripts to describe their tests, and for the framework to be able to access those descriptions w/o actually running the test. (blue-skying it here..) -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!"
