Change impact¶
The Web Change impact view shows where a requirement chapter or reusable test-step block is used. It helps you determine the testing scope after a change. Analysis does not modify cases, templates, runs or results.
Review a scope¶
- Open Reports > Change impact and select a requirement chapter or reusable step block as the source.
- For requirements, optionally select a reference baseline. Without a baseline, the view reports associations without claiming that content changed.
- Review library, template, open-run and open-retest uses. Search and context filters narrow the results. Use page navigation to see further entries.
- Open the relevant case or run and decide whether to synchronize a template or prepare a targeted retest. Analysis never performs these changes automatically.
Interpret the results¶
For requirements, comparison shows whether the chapter changed relative to the selected baseline. Not in baseline means the chapter was outside the captured scope. Current and previously captured case relationships can differ. An association through the library does not establish which requirement text applied to an earlier run.
For blocks, pinned revisions are shown alongside the current revision. An older revision does not necessarily mean the text in use changed: only expected results may have changed while a case uses just the steps. Steps, expected results and their inheritance are therefore reported separately. Detached local content is no longer a block use.
Templates and runs are analyzed from their actual saved block bindings. A newer library revision does not replace these copies. An open run is identified as a retest only when retest provenance was recorded. Completed runs are outside this view's scope.
Permissions and limits¶
An active project account and read access to the source and respective targets are required. Existing run permissions also apply: a project/test manager role or full access to the plan or run. Unreadable objects are excluded from rows and hidden aggregate counts. A readable planned case can be inspected even when its library source is unreadable; that source's identity is not disclosed.
Baseline comparison follows the complete baseline permission rules. A forbidden comparison never means unchanged. Results describe the current moment; reload after concurrent changes. Windows continues to use the project data but has no dedicated change-impact view.
MCP and REST¶
Read tools use the same permissions and results as Web. REST exposes them as POST /api/v1/operations/<tool-name>; see REST API.
| Tool | Use |
|---|---|
ztm_change_impact_source_options |
Find readable sources: sourceType is requirement or reusable-step; optional query, skip, take. |
ztm_change_impact_read |
Analyze a source: also pass sourceId as a string; optional baselineId for requirements only and context of library, template, open-run or open-retest. |
take is 1–200, default 50; skip is 0–100000. Search text is limited to 200 characters. HasMore indicates another page of readable results. The project.change-impact.read capability is read-only and does not authorize synchronization or retest creation.
Example block arguments:
{"sourceType":"reusable-step","sourceId":"<block-ID>","context":"template","skip":0,"take":50}