...

1. Run a change impact analysis from the Parasoft Change Advisor perspective.
2. Create a change template.

3. Apply that change template—on a case-by-case basis (to resolve specific change impacts reported by the change impact analysis) or for batch refactoring (to rapidly update all impacted tools across a project, suite, etc.)—to update your existing suite or create a new one.

...

1. Update your preferred test execution Test Configuration to perform change impact analysis as it executes tests.
2. If change impacts are reported:
   1. Create a change template.
   2. Apply that change template—on a case-by-case basis (to resolve specific change impacts reported by the change impact analysis) or for batch refactoring (to rapidly update all impacted tools across a project, suite, etc.) —to update your existing test suite or create a new one.

...

Once a change template is created, we recommend that you review and fine-tune the automatically - defined mappings that explain how elements/operations/resources and schemas from the original definition relate to those in the current definition. 

...

Reviewing and updating the automatically - defined mappings is performed in the graphical Change Template editor:

Once a change template is generated, it can be applied on a case-by-case basis (to resolve specific change impacts reported by change impact analysis) as well as for batch refactoring (to rapidly update all impacted tools across a project, suite, etc.)

...

Change impact analysis compares the service definition that was originally used to construct the tools’ messages  vsvs. either 

• The live version of that same service definition (at the same URL as the original definition file).
• A different service definition  (at a different URL than the original definition file).

...

• If you suspect that the service changed, run it from Change Advisor to identify what changed and see the scope and nature of the updates that will be required to address that change.
• If you’re not expecting any changes, run it alongside normal test execution. This way,  if if a test fails, you can immediately determine if that failure might be related to a change in the service.

...

The refactoring will update messages as defined in the change template. Tools for removed operations will be disabled , but not deleted.

Anchor
Defining a Change Template Defining a Change Template

Defining a Change Template

...

1. If you have not already done so, run a change impact analysis as described in Identifying Changes with Change Impact Analysis.
2. Ensure that the Service Catalog shows the service that has changed and contains "versions" for both the original service definition and the current service definition.
   • To add a service to the catalog, right-click any where anywhere in the Service Catalog view, choose Add Service to Catalog, complete the available fields (these vary based on the artifact type selected), then click Finish.
   • To add a version to the catalog, right-click on the related service, choose Add Version to Catalog, then specify the necessary version details.

   • To rename a service or version, right-click its Service Catalog node, then choose the appropriate Rename command. The names specified here will be used in the Refactor Using a Change Template wizard.
     
     

     Info
     icon false title Why Are There Two Operations Nodes in the Service Catalog?
     Note that if you have both SOAtest and Virtualize installed, the Operations node will be split into two nodes: • Client View: For SOAtest messaging clients (covers request parameters) • Responder View: For Virtualize message responders  (covers response parameters)

3. Do one of the following:
   • Choose File> New > Change Template.
   • In the Service Catalog, select the nodes for the original version and the new version, right-click the selection, then choose the appropriate Add Change Template command.
   • In the Service Catalog, right-click the Change Templates node for the original version, then choose Add ChangeTemplate.
4. In the wizard that opens:
   1. Specify basic information about the change template.
      • Note that if you have both SOAtest and Virtualize, you will see an option to create a change template for clients or responders. Choose Client if you want this change template to define how to update requests in SOAtest messaging client tools. Choose Responder if you want this change template to define how to update responses in Virtualize message responder tools.
   2. Click Next.
   3. Specify the name and location for the change template file that will be created.
   4. Click Finish.

...

Each element’s schemas are mapped in the Map Schemas tab.

 

 As you are reviewing the mappings, you can use the filters available at the top of the editor to focus on high probability matches, matches needing review, or unnmatched unmatched items. 

As you review and modify the change template, you can perform the following actions: 

...

For a tutorial on using Change Advisor, see Updating Tests as Services Change 1.