On 2006.09.06, Rusty Brooks <[EMAIL PROTECTED]> wrote: > It's funny... I know we're all experienced developers and that > therefore all of our viewpoints have validity, but to me debugger > test > cases. I am really doubting you are going to have enough test cases to > cover all conceivable reasonable inputs.
If your code under test is capable of doing so many things that you can't create a reasonable list of testable items, then I firmly assert that your design is overly complex and requires simplification and refactoring. Some truths I've discovered along the way: * Good code is easy to test. * It's really hard to write good code. * Most code isn't easy to test, because it's not that good. Then, if you drink the test-driven development Kool-Aid, you start to discover: * Writing tests first nudges you in the direction of better code. > This is not meant to be a barb, but, for example, do you have a > test-case that examines what happens if someone ns_returnredirects and > then doesn't do an ns_adp_abort before the end of the page? We should have a test case for this, yes. Unfortunately, AOLserver lacks reasonable automated tests, at the moment. > AOLServer contains a programming language and an extensive API, MANY > of the commands have unexpected interactions that you don't even know > about yet. This is because much of the functionality lacks tests. This is something we definitely need to address. -- Dossy -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
