New in 0.1, 2005-04-12:

• Strategies:

  Many strategies are already available.

  • Concrete strategies
    • Suite strategies: Suite, Pool, Glob
    • Command based strategies: Cmd, SubCmd, SignalCmd
    • Unit test strategies: RUnit, JUnit
    • Packaging strategies: Package, Checkout, Make, PackageCollection, Bootstrap, Authors, Configure, Compile, Clean
    • Distributed mode strategies:
      • unstable/testing: DistDuplicate, DistDelegate, Distribute
      • stable: Tester, Fetch, Fetcher
    • Basic and useful strategies: Sleep, Block, KillAll, Import
    • Elementary strategies: Pass, Abort, Error, Fail, Stub
    • Test strategies: Test, ProbabilityThreshold
    • Database strategies: SqlQuery
  • Abstract strategies:
    • Strategy
    • Composite
    • Collection
    • Proxy
    • IOBased
    • CmdBase
    • DistStrategy
• Loaders:

  A YAML loader is provided to easily write the test suite.

• Dumper:

  A YAML dumper which follow the same format than the YAML loader provides a human/script readable way to dump the suite result. An XML dumper is also available to easily put online the suite result.

• Logger:

  A specific Logger which manage a severity level, a verbosity level and a section tree. Dumpers and/or Filters can be plugged to it.

• Filters:

  Only two basic filters: Saver and BasicLogger. The filtering system is not yet very developed.

• Statistics computation system:

  TTK computes a weighted average of the succeed test of the test suite. This system is extensible to allow other kinds of computation.

• A functional environment which handle shared values between strategies.
• Distributed mode:

  This feature of TTK is still unstable but already provides some interesting result. It is based on a specific daemon running on remote machine.

• Cache system:

  TTK remembers the successful test across session. Not yet fully tested, but already usable.