Hi Philip,
You labast the lack of testing tools but one of the other blog posts [1] is about how you built a testing framework.
We're just just being kind in that blog post because you didn't really spell out any shortcomings then ?
[1]
You labast the lack of testing tools but one of the other blog posts [1] is about how you built a testing framework.
We're just just being kind in that blog post because you didn't really spell out any shortcomings then ?
[1]
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.