>>>>> On Fri, 21 Dec 2007 13:34:49 -0600 (CST), Dave Rolsky <[EMAIL PROTECTED]> >>>>> said:
> However, usually I end up needing to investigate aspects of the > testers platform, often by having them run snippets of Perl code from > the shell, or asking them to try a patch. There's not much you can do > to automate that. I'd argue that without any change to today's practice there is a very easy way to automate this and it goes like: 1. You get a fail report with an error message that doesn't tell you exactly what went wrong. 2. You rewrite your test in a way that it does tell you more. 3. Release. 4. If you now understand the problem, fix it, else goto 1. > As chromatic mentioned, failures often happen on platforms to which I > as a module author don't have ready access, so I need some assistance > from the user of that platform. You're right, there may be cases where you have no idea into which direction to continue, but 99% of the time you *as a programmer* should be able to solve the problem without talking to the tester. -- andreas
