On 2006.09.06, Tom Jackson <[EMAIL PROTECTED]> wrote: > Anyway, the code that is causing the segfault is very likely to be the > type of thing that you could never write a test for. And writing a > test right now, just to make sure it doesn't happen again seems > equally impossible.
Of course you can write a test for it. Create an ADP page that issues a ns_returnredirect, starts a server with a stripped down test config, and then hit the server (wget, curl, Tcl http package, etc.) and verify that it returned the correct response *and* didn't exit with a signal. > Also, the bug I (re)fixed this weekend would never be > testable....but........ If you can reproduce the bug, it's testable. If you can't reproduce it, I assert that it's equally hard to fix as it is to test for. If you understand what the problem is enough to fix it, you should be able to elicit the condition through a test. Otherwise: how do you verify that your fix actually, well, fixed it, if you can't manually test the before-and-after conditions? And, if you can manually test it ... why can't you automate it? -- 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.
