...
| Info | ||||
|---|---|---|---|---|
| ||||
Change Advisor depends on an Eclipse plugin called EMF Compare. That plugin gets installed in the full SOAtest installation, but not when SOAtest is installed from update site or plugin installer. You can install the EMF Compare plugin using the Eclipse update site mechanism; the update site is at httphttps://downloadarchive.eclipse.org/modeling/emf/compare/updates/releases/2.0 |
Workflow
If you suspect that a service has changed, the typical workflow is:
...
When a Change Impact Analysis is run, Change Advisor reports how assets’ messages are impacted by a change in the related definition file (e.g., WSDLOpenAPI/Swagger, schemaRAML, WADL, OpenAPI/SwaggerWSDL, RAMLSchema). This analysis can either:
...
- On a test-by-test or responder-by-responder basis
- On a selected set of test or responders
- On all applicable tests or responders in a suiteOn all tests or responders in a suite
...
Change Advisor can be applied to messaging tools (SOAP Client, REST Client, EDI Client, Fixed Length Client, Message Stub) in SOAtest. It can also be applied to Message Responders in Virtualize.Change Advisor operates on the messages specified via Form Input if the tool is set to be constrained to WSDL or Schema, or if the Service Definition has a an OpenAPI/Swagger, RAML, or WADL (SOAtest) , or OpenAPI/Swagger specified. It operates on the messages specified via Form JSON if the Service Definition has a an OpenAPI/Swagger, RAML, WADL (SOAtest), or OpenAPI/Swagger specifiedor WADL specified. If a tool’s message is specified in a non-supported format, it will be skipped during analysis and refactoring. To update values in these formats, values in other non-message fields in these tools, or values in tools not supported by Change Advisor, use Parasoft Search and Replace. See Updating Tool Values with Search and Replace.
...
- The standard asset explorer: This lets you select which assets to analyze or refactor (by applying the toolbar buttons described below).
Toolbar buttons: Three buttons are added: Run (used to rerun change impact analysis to check that assets have been refactored properly), Perform Change Impact Analysis (described below), and Refactor Using a Change Template (described below).
- The Service Catalog view: This stores information about the different versions of each service, as well as the change templates that define how one service version’s structure compares to another’s.
- The Properties view: This provides details about the item selected in the Change Template editor.
- The Change Impact progress view: This reports the progress and results of change impact analysis.
- The Quality Tasks view: This is where you can review change impacts and refactor the related tools using any available change templates.
...
- 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 a test fails, you can immediately determine if that failure might be related to a change in the service.
Running Change Impact Analysis from Change Advisor
To run change impact analysis from Change Advisor:
...
For instance, assume you have selected a suite that includes assets based on 3 three different service definitions. Analysis with the Scan the selected assets against their current service description option will compare all of those assets vs. the current version of their correlated service definitions. If you select Scan the selected assets against a specified service description—and you specify the location of the existing and updated version of 1 one of the 3 three service definitions used by those assets— the analysis will be applied to only the assets that use that specified service description. Assets based on the 2 two other definitions will not analyzed.
Running Change Impact Analysis During Regular Test Execution
Running change impact analysis during regular test execution can help you identify when your tests need to be updated to reflect a service change. To run change impact analysis (vs. the current version of the assets’ existing service definitions) during regular test execution:
- Configure your preferred execution Test Configuration to perform change impact analysis. Change impact analysis is enabled/disabled in the Execution> Execution > Change Impact tab.
- Run test execution with that Test Configurationthat Test Configuration from the user interface or using the command line interface.
Reviewing Analysis Results
As the analysis runs, analysis progress will be reported in the progress view as well as the console view. Note that if an asset is reported as "skipped," this indicates that it did not have messages specified in a supported format (e.g.for example, Form Input).
The results of the analysis will be reported in the Quality Tasks view. A A Change Impact layout is provided to help you review change impacts. If the Quality View is not already using this layout, you can enable it by clicking the Change Impact Layout toolbar button in the results view:
You can also open this layout from that view’s drop-down menu.
The results are organized by service, suite/location, and the type of change:
In addition to the Quality Tasks view, the results of the analysis will be reported in associated HTML reports. Note, however, that change impact analysis results are not shown when test results are uploaded to DTP.
Exploring the Change Impacts
...
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:
| To achieve this... | Do this... |
|---|---|
| Specify that two unmapped items are correlated. | Select both items, then click Connect. |
| Specify that two mapped items are NOT cor-relatedcorrelated. | Select both items, then click Disconnect. |
| Specify the default value for an unmatched item. | Right-click that item, select Configure Default Value for Added [item_name], then specify the appropriate value in the dialog that opens. |
| Indicate that a "match needing review" has been reviewed (turning a yellow mapping to a green one). | Right-click any area of the mapping, then choose either Mark Match [mapping] as Reviewed or Mark Match [mapping] and Child Matches as Reviewed. |
| Indicate that an unmatched item has been reviewed. | Right-click that element, then choose either Mark [item_name] as Reviewed or Mark [item_name] and Children as Reviewed. |
...