comment on

I'm not sure where you read that I was advocating throw away tests.

My point was it's a top-down process with different layers of tests and POC.

The API tests of the top layer are stable, the POCs less so.

There is no point in starting a long endeavor without

clarifying the clients expectations
proving the feasibility

This is best done with some demo code, and this can and should be tested. Written specifications are open for interpretations, tests let you sleep well.

Since those tests define your API they can't easily be thrown away anymore unless your POCs were bad.

Hope my perspective is clearer now.

Cheers Rolf
_{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)

Wikisyntax for the Monastery}

In reply to Re^8: What to test in a new module by LanX
in thread What to test in a new module by Bod

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.


go ahead... be a heretic
	PerlMonks