Testing Upgraded Applications

Many of the same testing principles apply when working with upgraded applications.  However, there are certain differences in the process that are worth noting.  Here is a list of FAQs that are answered in the 21st and last chapter of the Migration Guide that ArtinSoft has prepared.  Check it out and if you have further questions I'll be happy to discuss them with you.

• How many approaches can I take to test an upgraded application?
• Why should I test my upgraded application?
• What are the basic steps in a testing process?
• Why is the test plan so important?
• What methodology should I follow to test my application?
• What items should be included in a test environment?
• Is it necessary to review the design of the application during the testing process?
• When reviewing the upgraded code, what actions must I take?
• What does ‘unit testing’ mean?
• Why should I perform black box testing on an upgraded application?
• In the context of white box testing, what does ‘profiling’ mean?
• What are the most commonly used test strategies for upgrade projects?
• What tools can be used to automatically test VB.NET applications?

Link to Testing Upgraded Applications