Personal tools

TBC

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
m (++category)
 
(One intermediate revision by one user not shown)
Line 6: Line 6:
 
* Integration with existing testing tools, HUnit and QuickCheck.
 
* Integration with existing testing tools, HUnit and QuickCheck.
 
* Integration with Cabal: if Cabal can build your code, TBC can too.
 
* Integration with Cabal: if Cabal can build your code, TBC can too.
* Bulletproof: TBC will try to run your all of your test files, even if some don't compile, and even if your project doesn't compile.
+
* Bulletproof: TBC will try to run all of your test files, even if some don't compile, and even if your project doesn't compile.
 
* Conventional: If you follow some common conventions, you write much less boilerplate.
 
* Conventional: If you follow some common conventions, you write much less boilerplate.
   
Line 16: Line 16:
   
 
[http://github.com/peteg/TBC/ TBC at GitHub]
 
[http://github.com/peteg/TBC/ TBC at GitHub]
  +
  +
[[Category:Development tools]]

Latest revision as of 02:38, 26 December 2012

[edit] TBC: Testing By Convention

Testing is a continuation of type-checking by other means.

TBC is a testing harness that frees you from writing boilerplate and makes your tests useful to you while developing. Its key features are:

  • Integration with existing testing tools, HUnit and QuickCheck.
  • Integration with Cabal: if Cabal can build your code, TBC can too.
  • Bulletproof: TBC will try to run all of your test files, even if some don't compile, and even if your project doesn't compile.
  • Conventional: If you follow some common conventions, you write much less boilerplate.


Authors: Peter Gammie and Mark Wotton.

TBC on Hackage

TBC at GitHub