The TBC package

[ Tags: bsd3, library, program, testing ] [ Propose Tags ]

TBC is a harness for running tests, relying on other libraries such as QuickCheck and HUnit to do the actual testing. If the tests follow conventions, TBC lets you skip a lot of boilerplate.

[Skip to Readme]


Versions 0.0.1, 0.0.2, 0.0.3
Dependencies base (==4.*), Cabal, directory, filepath, process, unix [details]
License BSD3
Copyright Peter Gammie, Mark Wotton
Author Peter Gammie, Mark Wotton
Category Testing
Source repository head: git clone git://
Uploaded Mon Jul 27 01:06:33 UTC 2009 by PeterGammie
Distributions NixOS:0.0.3
Executables tbc
Downloads 1077 total (81 in the last 30 days)
Rating (no votes yet) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Docs not available [build log]
All reported builds failed as of 2016-12-31 [all 9 reports]
Hackage Matrix CI


  • Test
    • Test.TBC


Maintainer's Corner

For package maintainers and hackage trustees

Readme for TBC-0.0.1

[back to package description]
= TBC: Test by Convention =

TBC provides two 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.

Inspired by test-based development, our aim is not to displace
existing tools such as QuickCheck and HUnit but to make a project's
tests more useful when things are in an inconsistent state. TBC is
also useful for supporting 'what-if' experiments, aiding program

TBC is presently alpha. It has proven useful to the authors but is
embryonic in many ways.

The directory 'Sample/' contains a sample project following TBC
conventions. We suggest running 'tbc' in that directory as a quick way
of understanding what it can do.

== Conventions ==

Tests live in $PROJECT/Tests. Test-specific hierarchical modules can
also exist there.

Within a test file, lines beginning with _ should _ when evaluated:

"exception_" / throw an exception.
"hunit_" / be HUnit tests: TBC applies "runTestTT . test" to them.
"ok_" / not throw an exception.
"prop_" / be QuickCheck tests: TBC applies "test" to them.
"test_" / be boolean tests (of type Bool or IO Bool or IO () with a
print statement or ...): TBC runs them and expects the final line of
output to be "True".

The tests themselves must ensure the test framework (QuickCheck, etc.)
is in scope, i.e. be executable as they are in GHCi.

The 'tbc' executable will search upwards for a '.cabal' file and
assumes the 'dist/' directory is in the same place.

== Invocation ==

There are two ways to use TBC:

- as a Cabal 'test' hook. This is not recommended as packages that do
  this cannot be uploaded to hackage. Perhaps changes in Cabal will
  make this more useful.

- invoking the 'tbc' executable.

The 'tbc' executable will search upwards in the directory hierarchy
for a .cabal file, and then go looking for tests in the current
directory and its children.

Presently it is best to run 'tbc' in the directory containing the
tests (or a subdirectory of it).

== Gotchas ==


tbc -v

for a verbose session.

It seems that the parts of Cabal that TBC depends on change
frequently. TBC has only been tested with the latest Cabal (>= 1.7)
from the darcs repository. It is probably not difficult to make it
work with earlier Cabals.

Conventions must retain the full name of the test, otherwise we run
into some nasty lexical issues, e.g. to avoid:

hunit_prop_blah =tName equals= prop_blah

We only support GHCi on *NIX presently.