|
From: Keith P. <kp...@bi...> - 2005-03-31 02:59:08
|
OK, I'm a pretty accomplished AS programmer, but I'm a bit new to the whole unit testing thing. While there are obviously plenty of resources for the subject in general, I have a few questions on the ASUnit implementation. I've done the quickstart, and I think I pretty much understand what is going on there. So now I move forward to testing my own existing classes. I have my whole package directory structure with my class files in it. 1. Am I supposed to create a new fla in the top level of that and run the Create Class command there? 2. This creates a lot of test files that are intermingled with my actual class files. Is this usual, expected, normal? 3. It doesn't seem like it does, but I want to confirm that CreateClass does not modify any of my existing class files. 4. So I should run create class on each class that I want to test? 5. when and why would i run the Build Test Suites command? 6. It's my understanding that unit testing could/should be built right into the compile process, so that your tests are run with each compile. Assuming this is true in principle, is this the expected work flow for Asunit? If so, should I create an AllTests instance right in my main application code somewhere, at least while building and debugging? Or it more just done via a separate fla just for that purpose? 1-4 I think i pretty much know the answers to, and have pretty much confirmed in my playing around with it. But hopefully I can elicit some tips and tricks, advice, etc. Lastly, is there any more documentation on asunit specifically, that I am missing? If not, I would be glad to help produce some, once I get up to speed on it. Keith Peters kp...@bi... www.bit-101.com |