On Thu, Oct 9, 2014 at 2:17 PM, Tim Mackinnon <tim@testit.works> wrote:
Any thoughts/pointers?
I would tend to create one test trait for each application trait the same way I create one test class for each application class. That exactly what I did with the Nile stream trait-based library (there is a journal paper about this library but I don't remember if it covers the unit-test). The source code is available at http://www.squeaksource.com/Nile.html. You can look at the unit tests for the collection library that are entirely based on traits (but the collection library itself is not). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill