In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Chris Devers) wrote:
> On Thu, 24 Feb 2005, Robert wrote: > > > I am trying to wrap my head around testing. What exactly do you test? > > I do mostly scripts for admin stuff and not modules. My scripts do > > things like run a program and then email the generated log file to me. > > Would you test that? What fits the criteria for "it needs a test"? > > That's a very big, very open-ended question that you're asking. > > In general, maybe "test all assumptions" is a good starting point: test > all input rigorously, test all dependencies meticulously, and be sure > that the output your code produces is consistent & predictable. > > But I'm not sure how to pin down general tactics for general testing. > Reading _Programming Perl_ chapter 24, "Common Practics" would be a good I will read that chapter... > start, as would all of the superb _The Practice of Programming_, which > isn't really a Perl book, but then this isn't really a Perl question. I also have the Perl Medic book which I am reading... Robert -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
