Hello, Mark and I would like to announce our test harness, which has features complementary to existing harnesses. TBC provides two main features: - It attempts to compile and run all tests, even if some do not compile or run. - Aspiring to the write-it-once principle, tests following conventions require a lot less boilerplate. It is at an embryonic stage of development, and would greatly benefit from feedback and/or patches. :-) Hackage: http://hackage.haskell.org/package/TBC git: http://github.com/peteg/TBC/ Enjoy! cheers peter -- http://peteg.org/
On Sun, Jul 26, 2009 at 6:12 PM, Peter Gammie
Hello,
Mark and I would like to announce our test harness, which has features complementary to existing harnesses.
TBC provides two main features: - It attempts to compile and run all tests, even if some do not compile or run. - Aspiring to the write-it-once principle, tests following conventions require a lot less boilerplate.
It is at an embryonic stage of development, and would greatly benefit from feedback and/or patches. :-)
Hackage: http://hackage.haskell.org/package/TBC git: http://github.com/peteg/TBC/
Enjoy!
cheers peter
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
Can it return an exit status based on whether or not all tests passed? If not, that would be a very useful feature that I have not seen in any other testing frameworks. Alex
On 27/07/2009, at 2:26 PM, Alexander Dunlap wrote:
Can it return an exit status based on whether or not all tests passed? If not, that would be a very useful feature that I have not seen in any other testing frameworks.
It could, and that's probably true of the other harnesses out there. The git repo for TBC now has this feature; it's a bit of a hack as some of the functions in Cabal that TBC uses have overly restrictive types. cheers peter
participants (2)
-
Alexander Dunlap -
Peter Gammie