Testing the results of synchronization

After synchronizing versions of an application, you should examine and test customizations in the Target configuration.

A test environment should be similar to the updated production environment, with forms accessing the updated IDOs, application database, and other parts of the application.

At a minimum, you should plan to testthese things:

• Customized forms in which you kept a customization in response to a FormSync prompt
• New forms that you created, including copies of Vendor versions of forms saved under a new name
• Forms that use a customized global object that you kept in response to a FormSync prompt

Consider dependencies within a form and within the system. An upgrade can modify any or all of these things:

• An IDO or other resource on which the customized object is dependent
• A Vendor version of a form or global object on which the customized object is dependent
• A Vendor version of a form or global object that depends on the Vendor version of the customized object

The effects of such changes are not transparent, and they must be considered in your test plan.

When there is a change in component type (for example, from radio button to toolbar button), you might have to adjust the size and position of the component.