|
From: Luke B. <lb...@gm...> - 2004-11-03 21:39:16
|
Hey David, I'm going through the list archives right now and answering items one at a time as needed. Thank you SO much for helping out on this list - you're answers are greatly appreciated. So - Regarding the addition of a fail method on the Assert Class, I'm adding it right now and it will be implemented in the next release. Thanks for that. Regarding the "Tests are allowed to continue after an assertion fails" issue: I actually like to get all of my failures at once, but I concede that it's probably easiest to accept a failure, fix it, and get the next one. Maybe you could add the requested functionality (stop on failure), but implement it with a Flag that will let users turn it on and off? I want to make sure that if you're going to submit code fixes, please make them Flash 6 player compatible - meaning no "Try-Catch" as it's critical that our Unit Test framework remain compatible with that player environment for the time being. At least until a more robust version is released on Pocket PCs. Regarding the construction of a more legible error message in the Assertion class. If you're interested in revising the way the UI outputs errors, I would be very interested in making that more like JUnit. Thanks, Luke Bayes |