>>The assertion has been made that typical applications have between 40%-50% of their code actually run during testing.
>>
>>I am curious to see what percentage of code you test (actually run during development/unit test/system testing) for:
>>
>>1) The development of a system from scratch.
>>
>>
>>2) The development of a new/replacement system but using code parts (including classes, functions, etc.) from existing and well-running systems.
>>
>>
>>3) Developing revisions to an existing application.
>>
>>
>>Thanks for your reply.
>
>Jim;
>
>The following seems funny but I heard it with my own ears.
>

Thanks for the reminder, Tom :) I was recently called to the user. I guess, she put some huge date (I need to check, if I verify the dates correctly) and the program went to a long loop. Trying to stop it she hit one of F keys and some macro was inserted into the data... I made an update in the Developer copy, but we didn't move them to Live yet...


>A user calls a developer and says, “The new application just crashed”!
>
>Developer: “What combination of keys did you use”?
>
>User: Gives the developer the answer.
>
>Developer: “You should never use that combination of keys”! (hint: Use an accent like a commander at a Nazi prisoner of war camp to give this statement that feeling of true authority.) The develooper was German by the way.
>
>That was the solution at one place I worked at. Making things more stable was not on the agenda. Ship product. Make profit. Go public. Make millions and millions. Loose customers. Go out of business.
>
>Yes, it is good to have a business plan and show it to your employees or perspective employees as well as your investors.
>
>To paraphrase the line from “The Treasure of the Sierra Madre”, “Testing, what testing? We don’t need no stinking testing”!
>
>Tom