Dummy Saves the Day!

Software is constantly changing.  Why?  There are 3 main reasons:

Software is constantly changing.  Why?  There are 3 main reasons:

1. Marketing and management want new software and/or enhancements to existing software to help increase sales.

2. Constant demand for new features from the users of the software.

3. New releases in the Operating System may require modifications to software.

Most experienced developers try to make their software bug free.  But, it’s not uncommon for them to “break” working code with these enhancements.  This can cause error conditions, alter results, or change logic.  Can’t they test every piece of code?  Not realistically, especially in the timeframe in which they have to work.  How many times have you, yourself, written a document, spellchecked it, proof read it, even had someone else read it, and it still has errors in it?  You can’t always catch every mistake.

I’m urging you to take an important step before you go “Live.” When you acquire updates to software, before you go live, test it with your company’s data. Your data may create challenges that the developer never, ever, would have thought of.  Every company, no matter how big or small, has quirks that no other company has. 

I know you claim that you test, but I mean REALLY test it, right down to the most elementary item.  It makes sense to create a dummy company on your system, and include your company’s “quirks” to challenge the new software.  Make sure you document what the expected results should be, so you can compare results during your testing.  Be sure to include quarterly and annual procedures and reporting.

Regardless, always test each and every update.  I know this takes time, but it will be less time than the time required to recover from a serious error in the software.  Don’t be the dummy!  Let your dummy save the day!

Have fun!

Posted by on 01/24 at 10:13 AM

My dad was a test conductor on the Lunar Module.  Because of that experience, he was a great proponent of what he called “end-to-end testing”: just because various sub-systems might work individually doesn’t mean the whole system will do the job for which it was designed.  The same applies to software: even if developers take the time to test more than their own contribution (most don’t), they cannot always anticipate how software is used in the field.  An end-to-end test on a dummy company is good advice.

Posted by  on  01/28  at  11:45 AM
Page 1 of 1 pages

Name:

Email:

Location:

URL:

Smileys

Remember my personal information

Notify me of follow-up comments?

Submit the word you see below:


Next entry: R.T.D.M. !

Previous entry: A Small World After All

<< Back to main

Members:
Login | Register | Add Post | Member List

May 2008
S M T W T F S
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31

Search


Advanced Search

Syndicate

Join our Mailing List