...
- Run a change impact analysis from the Parasoft Change Advisor perspective.
- Create a change template.
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.
...
...
SOAtest
...
can catch unexpected service changes as soon as they occur:
- Update your preferred test execution Test Configuration to perform change impact analysis as it executes tests.
- If change impacts are reported:
- Create a change template.
- 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.
Change Impact Analysis
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., WSDL, schema, WADL, Swagger, RAML). This analysis can either:
...
What Changes Does it Cover?
...
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 RAML, WADL (SOAtest), or Swagger specified. It operates on the messages specified via Form JSON if the Service Definition has a RAML, WADL (SOAtest), or Swagger specified. If 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
...
the following chapters:
...
the following chapters:
...
- SOAtest:
- Updating Tool Values with Search and Replace 1
- Virtualize: Updating Tool Values with Search and Replace
...
The Change Advisor UI
The Change Advisor perspective is designed specifically for identifying and addressing change impacts.
...
Change impact analysis will report only changes that are relevant to the tools you’re analyzing. For example, if the service no longer includes an optional element that your tools never used, a change impact will NOT be reported.
...
Typical use cases for running change impact analysis in SOAtest are:
- 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
...
The results of the analysis will be reported in the Quality Tasks view. 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:
...
results are organized by service, suite/location, and the type of change:
...
Exploring the Change Impacts
...
If your team wants to share change templates, either share the project that contains that template, or copy the template from one workspace to another.
...
Tutorial
For a tutorial on using Change Advisor, see Updating Tests as Services Change.