Testing support is basic and, when we started, there were no clear best practices - so we published how we organized our repo.

The `@test foo` command basically raises an exception if the result is false. You have to manually register all of the tests and call them individually. setUp and tearDown has to be done manually. The testing library keeps no data about how many tests were run - it just throws an exception if an `@test` encounters a false.

It works, but there is no sophistication.