Testing, testing, testing...do we really need testing? The answer is YES! Always! The big questions are:

1. How do I test?
2. What do I test?
3. Do we just do program testing or do we include testing data quality?
4. What about volume testing?
5. Who signs off on after-test completion?

For a conversion project, we need to create a list of exactly what we need to test. For example, we may need to create testing scenarios that are run in both our source system and target system. Count the number of records, and then dive into the data by types, codes and statuses; use a profiling tool if you have one. Uncovering disconnected (outliers) is always at the top of my list. The results can be used to test the target system after conversion. You should document any translations, filtering and excluded records.

If there is a reporting front-end and/or software front-end, you will need to write testing scenarios to make sure the reports and the software are performing as expected.

Staying organized is key to your project's success. I seem to use a lot of spreadsheets to keep track of all the testing that is required for a conversion. I have had some clients who use specific software to keep track of all the testing scripts, and who use testing tools that simulate volume and system saturation.

There seem to be lots of choices when it comes to testing tools, but the important thing is to decide up front how the testing phase of the project should executed, monitored and reported. How do you outline, execute and organize your project testing? Share your thoughts below.