Have you explained to them that in the long run, this cuts down on development time?

I spend time testing, debugging, retesting, re-debugging - and would say my new projects take 4x as long as they could take.

I am under no pressure to do it one way or another. Personally I am trying to save myself time. I can start up a project, make it look finished in x time. I know it will be ok for a while. I just know that in 365 days, someone will come b1ch1n9 that something blew up somewhere. No way.. This makes a company look like crap, for one. It's embarrassing, and it can be an unholy mess.

If your stuff is for more then one client.. spend the time, please. We know you can't predict exactly how long some of this stuff will take. We also know they want to hear a number. Will you tell them the honest truth or a pretty lie? I think the pretty lie will ultimately cause the most harm. What do the people you work with think about this? They are the best people to ask. And you have to trust them with their judgement and honesty.

In reply to Re: Adding Unit tests to the development cycle by leocharre
in thread Adding Unit tests to the development cycle by Sifmole

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.