Difference between revisions of "TBC"
Jump to navigation
Jump to search
m (++category) |
|||
(5 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | + | = TBC: Testing By Convention = |
|
''Testing is a continuation of type-checking by other means.'' |
''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: |
||
− | TBC is a testing harness... |
||
+ | * 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: [http://peteg.org/ Peter Gammie] and [http://shimweasel.com/ Mark Wotton]. |
Authors: [http://peteg.org/ Peter Gammie] and [http://shimweasel.com/ Mark Wotton]. |
||
[http://hackage.haskell.org/package/TBC TBC on Hackage] |
[http://hackage.haskell.org/package/TBC TBC on Hackage] |
||
+ | |||
[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
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.