Hmmm...what I'm hearing you say is that, during development, tests should be written not just for individual routines but for larger and larger blocks of routines.

That sounds good.

I do worry about the possibility of combinatorial explosion in the number of elements that will be tested...but that's probably a false concern, since you only need to worry about testing blocks of routines that are actually used together. Hmm.

At the same time, I don't think you can do away with the acceptance testing phase. The point of that phase is not to reveal bugs...the point is to prove TO THE CUSTOMER that the product works as required.

Thanks, this is definitely the kind of thing I was looking for.


In reply to Re^2: OT: Agile programming; velocity during testing? by Whitehawke
in thread OT: Agile programming; velocity during testing? by Whitehawke

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.