I guess I'm not communicating my point clearly. I don't see any point in writing tests for a first draft of a spec implementation/POC. No client is going to communicate their requirements in a manner that's not going to require iteration on both ends unless they're coming to you saying "we need to integrate with this API" which is an existing specification that has known inputs and outputs regardless of the quality of the API. POC and demos have only as good of a chance of being correct as the requirements dictating their implementation and the quality of communication to do so.

Starting with demos, POCs and tests for the main features should minimize that risk.

I'm not sure how tests minimize risk in a POC unless you're using them as something that's black and white in terms of an API contract that says "hey these are the requirements that were communicated and this is proof that they were coded to spec." I feel like it's much harder to iterate into a concrete state quickly if you have to change tests 2-3 times before you and your client reach a consensus.

Anyway I'm probably not going to get my point across any more effectively at this point so hopefully someone finds some sort of value reading through this.

Three thousand years of beautiful tradition, from Moses to Sandy Koufax, you're god damn right I'm living in the fucking past

In reply to Re^13: What to test in a new module by stonecolddevin
in thread What to test in a new module by Bod

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.