TBC
From HaskellWiki
(Difference between revisions)
m |
|||
| 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 | + | * 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. | ||
Revision as of 05:20, 29 July 2009
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.
