'''What?'''

PTL is a sugary/pretty wrapper over [tcltest], a typical looks like:

   Name: expr-1
   Description: Check that number + 0 equal to number
   Result: 6
   Test: {
     6+0
   }

It is currently being used for testing Wind/Diesel Systems at Powercorp [http://www.pcorp.com.au] in Darwin, NT, Australia by Phil Maker [PJM]. 

'''Why?'''

The first question is why bother with a wrapper, just use [tcltest], well:

   1. This little rubber duck does not want to write the tests. The moment I show them tcltest the users/engineers eyes glaze over and they look happy saying well we willjust do the specification Phil, and you can write the tests :-). They seem to be happy enough the prettified version above, must be something about too many -,{,} characters scaring them.
   1. The tests (well some at least) need to be written as part of the specifications whcih are formatted in LaTeX and it would be nice if they looked pretty in plain text.
   1. Since its just TCL and tcltest we can do all those wonderful things such as writing our own control structures, generators, etc. One of the scary ideas was that we should our own natural looking test language/suite that would do what we want, the dreaded lollipop.

Beyond the sugar, the following things are required:

   1. Ability to ask/interact with a human being during test, e.g. to ask to open/close a switch or valve. [PTL: please]
   1. Ability to get a human being to check a result both during a test [PTL: check] and afterwards [PTL: Ask:]
   1. Generate some pretty reports which are just hacks to [tcltest] for now.
   1. And run using [after] some commands which read/write values from devices, control inverter load banks and do other magical things.

'''Comments/Additions/....'''