IBM Branch Transformation Toolkit 5.1 Migration and Usage Guidelines

54 IBM Branch Transformation Toolkit 5.1 Migration and Usage Guidelines

򐂰 com.ibm.btt.tools.gw.model.emf_5.1.0

򐂰 com.ibm.btt.tools.migration_5.1.0

Setting up the migration tool

The migration tool is a WebSphere Studio Application Developer plug-in that

helps you migrate your version 4.3 toolkit applications to version 5.1 applications.

If you installed the toolkit before installing the WebSphere Studio Application

Developer Integration Edition, copy the following plug-in files to the

wstools\eclipse\plugins\ folder of your WebSphere Studio installation folder:

򐂰 com.ibm.btt.tools.common_5.1.0

򐂰 com.ibm.btt.tools.chaeditor.model.emf_5.1.0

򐂰 com.ibm.btt.tools.chaeditor_5.1.0

򐂰 com.ibm.btt.tools.fmteditor_5.1.0

򐂰 com.ibm.btt.tools.fmteditor.model.emf_5.1.0

򐂰 com.ibm.btt.tools.struts_5.1.0

򐂰 com.ibm.btt.tools.webdiagrameditor_5.1.0

򐂰 com.ibm.btt.tools.bp_5.1.0

򐂰 com.ibm.btt.tools.gw_5.1.0

򐂰 com.ibm.btt.tools.gw.model.emf_5.1.0

򐂰 com.ibm.btt.tools.migration_5.1.0

2.5.4 Testing

Testing is an essential part of the migration process and cannot be overlooked.

Subtle changes can be introduced in your application’s behavior when you use

new software versions. Testing is the only way to discover any possible

problems. Normally, the migrated project already has an existing test scheme in

place, and in most cases, this can be used with little or no modification to test the

migrated application. Testing a migration effort can be executed generally in

much the same way as for a new release of your application, even when the

migration has resulted in significant changes to the application infrastructure or

core behavior.

New software specifications often introduce clarifications of details covered in

older versions and this can translate into subtle changes in application behavior.

As part of a migration, a full regression test of your application code might be

necessary to ensure that subtle changes have not introduced errors into your

application. The specifications are often the best source of information about

changes that have occurred. You should carefully study the specification

changes when planning and executing migration testing.