Parameterizations can get broken, especially after changes are made to a data source and/or its columns. SOAtest/Virtualize provides tools to help you troubleshoot situations like these.

Identifying and Troubleshooting Broken Parameterizations

SOAtest/Virtualize identifies assets and tests that have broken parameterizations with a warning icon in the Test Case Explorer and/or Virtual Asset Explorer.

Broken parameterizations are identified in a few ways:

1. Automatically when tests are run.
2. Automatically when you open a client or responder editor.

3. Manually when you right-click a project, asset, or test and choose Find Broken Parameterization in Client/Responder Payloads. If any issues are found, they will be reported in the console (see below).

For either of the automatic detection methods, you can right-click the asset or test (or any of its parent nodes, up to and including the project) and choose Find Broken Parameterization in Client/Responder Payloads to get more information about the issue. A dialog will appear with a summary of the issues found and detailed information will be printed to the console under the heading "Broken Parameterization Results." Issues will be sorted by responders and data sources.

The warning icon will be cleared when the test or asset is fixed, and the action is reapplied. The icon may also be cleared by right-clicking the test or asset or any of its parent nodes and choosing Reset Statistics.