Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

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

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others meditating upon the Monastery: (5)
As of 2024-04-13 19:23 GMT
Find Nodes?
    Voting Booth?

    No recent polls found