|
From: Robert S. <rob...@gm...> - 2007-04-09 20:54:46
|
Luke, I got a response from the asunit-users mailer daemon saying that my registration on the list had been confirmed, so I don't know why you are having to approve emails from me. If I missed a step somewhere. please let me know. I appreciate you efforts on this project obviously, but I think that auto-creating test-suites for every class is not necessarily the best way of going about things. I come from a .NET shop and in NUnit you give a class an attribute to define that it is a TestFixture. So when NUnit runs, it can pick up all of your tests and execute them. JUnit does something similar I am pretty sure. I am not terribly certain as to whether or not something like what I've mentioned above is even possible in ActionScript, but I would rather create TestCases by hand and call them by hand then to have them auto-generated for me. I just re-read your message, and now I am not sure what you are saying. Are you saying that both TestCases and TestSuites are created/maintained automagically, or are you saying that a test suite is modifed each time you add a test case to a project? The second is good the first is not. I don't want to have a TestCase in my directory structure unless I put it there. I've recently spent a good deal of time getting FlashDevelop up and running. I'd rather not go through that again with ASProject right now. I like using the best tool available, but I've barely heard anything about ASProject, so I don't think I'll be switching just yet. I am also pretty sure that there are alot of Eclipse users out there who would like to use your unit testing library that don't want to give up using Eclipse to do it. I think that you should consider that most people using a unit testing framework are probably fairly sophisticated users to begin with, so you should expect them to need some kind of tool to create tests for them. I write NUnit tests by hand, so surely I can write ASUnit tests by hand, and if I can't, maybe that should give you pause. Robert On 4/9/07, Luke Bayes <lb...@gm...> wrote: > > Hey Robert, > > Thanks for taking the time to write this up, we should definitely talk > more before you get too far. > > First off, please join the asunit-users list as I have to manually approve > emails from non-members and it causes a delay for your message to get out. > > Second - there are a small handful of tools available to help you build > classes, test cases and test suites (The AsUnit MXP, AsUnit XUL Ui<http://www.asunit.org/#getStarted>, > and AsProject <http://code.google.com/p/asproject/>). The XUL UI, will let > you configure your project however you want, but it has the drawback that it > has to be kept in sync with your Flex Builder project manually. The MXP and > AsProject tools expect your test cases to be in the same project space as > your source classes. This doesn't mean that your test source gets compiled > into your deployed application as the dependency checker in the compiler > should only find references to test features when compiling the Test Runner, > and not when compiling the main application. A single flex 2 project can > have many application roots, each of which will spit out a separate SWF file > based on what classes are referenced from that root. > > Please take a look at AsProject <http://code.google.com/p/asproject/> to > get some idea as to how we structure applications these days. We're actively > building tools that support this project layout and hoping that the > community will agree that it makes sense. If you choose to layout a project > differently, you will probably not be able to take advantage of these > features as they become available. > > Regarding your question of test suites, you can think of each ActionScript > test suite as a Composite <http://c2.com/cgi/wiki?CompositePattern>structure that contains any number of TestCases and other TestSuites. Each > of the aforementioned tools will automate construction of test suites so > that you can be assured that all of your tests are being executed. The only > time I manually interact with these files is when debugging some feature or > set of features, otherwise I usually just edit the Test Runner's start call > to execute the test case that I'm currently interested in, and then edit it > back to running AllTests before I check in. > > Hope that helps! > > Please keep the questions coming, I'm certain you're not the only one. > > > Luke Bayes > www.asunit.org > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Asunit-users mailing list > Asu...@li... > https://lists.sourceforge.net/lists/listinfo/asunit-users > > |