Testing is not about saving time in the short-term. Testing takes time and learning to write good tests takes time. I'd estimate that on my current project we spend anywhere from 25% to 50% of our time writing and maintaining automated tests. I find claims that you'll cut time on small projects by writing tests to be unsupportable. Larger projects may show gains as the complexity of a job mounts, but I don't have any hard data to show you.

One benefit of testing you didn't mention is increased flexibility. There are a whole class of changes that you simply won't do without a complete regression suite to back you up. Major refactoring is basically unthinkable without tests. That means that code without tests ages faster and has to be rewritten more often, a task with an enormous price-tag for a complex system.

I think your best bet is to give it a try and see how it goes. Tell your boss you think it'll add a small amount of time to the project but that the pay-off will be well worth the wait. If your boss is smart he'll understand why you can't be more specific till you try it!

-sam

In reply to Re: Adding Unit tests to the development cycle by samtregar
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.