Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The good news is that you should be able to say that the actual results of the original system define the expected results of the new system and this is a BIG leg up for defining test cases.

Image Added

Automated Unit Testing

Another extremely powerful technique to implement as part of your migration effort is automated unit testing. Automated unit testing is a natural extension of GMM's automated conversion pipeline:

...

That said, the GMM assumes a working source codebase, not a frozen source codebase. The legacy application is allowed to be maintained and enhanced for ongoing maintenance. Updated versions of the VB6/ASP/COM codebase may enter the translation refinement process as they become available – typically on the same release cycle as the legacy application.

Forms Designer Test

The Forms Designer Test verifies that the designer code in your .NET UI classes (Forms and UserControls) can run correctly in the visual Studio forms designer:

Test PlanNotes
Steps1. Open your .NET project in Visual Studio.
2. Open each UI class in the .NET forms designer.
Expected ResultsThe form or control is rendered properly and looks well formed.
 


Error ConditionThe UI class is not rendered properly, possibly all you get is an error listing.
 


Troubleshooting.NET Designer errors are difficult to troubleshoot because they typically occur in logic that instantiates UI controls which is hard to access and debug. You will begin the troubleshooting problem by reviewing the designer error report.
 


Resolution.NET designer problems can occur for a variety of reasons ranging from missing externals, to crude syntax errors, to more advanced compile time validation.
 


Once a designer error is resolved you should implement the fix in the migration configuration so that it will not occur in the next translation cycle.

 

 

...