Page History
...
The first part is to include traceability notes inside the Enterprise Test Case Designer plan identifying which part of the model is affected by which story (there are largely 3 categories you can see on the image below).
...
Potential improvement #1: Write story descriptions in Gherkin. That would not only improve the clarity and communication, but would also provide the kickstart to scripting in Enterprise Test Case Designer.
Potential improvement #2: Group parameters & values together in their own part of the story (similar to “Description” or “Acceptance Criteria”), in the mind map format (for visual analysis) and/or in the parameter table one (for direct import into Enterprise Test Case Designer). That speeds up the process of reading through paragraphs of text to identify the key model elements.
...
Potential improvement #3: Include the “mini scenarios table” that covers the most important interactions from the story (which can also be imported directly into Enterprise Test Case Designer). It can help clarify ambiguities in complex rules much sooner.
...
Potential improvement #4: Add “Enterprise “Test Case Designer” label and relationship link type “shares assets with”. Displaying both labels and links in the sprint board view will provide the quick view into possible connections and increase collaboration efficiency.
...
The primary method is exporting from Enterprise Test Case Designer into compatible CSV and importing into test management tools (like Xray). Enterprise Test Case Designer also supports export into the formats directly compatible with the execution tools at the last stage of the toolchain (like Ranorex Studio).
...
How to deal with changes
Once the Enterprise Test Case Designer model is built, the story link + traceability notes would map the requirement updates and let the user know which parts to change. The interaction coverage can be focused on the new areas via Mixed-strength and Parameter structure (e.g., more Value Expansions for less important parameters).
...
TCs in Jira/Xray would be updated via re-import, either for the full scope or only for the new elements using Freeze/Script features in Enterprise Test Case Designer.
If the execution history must be preserved, the import is typically either performed into a new repository folder/Xray test plan or with overwriting the existing Issue IDs. Also, Xray Archive function or this solution (the new test execution item) can also be considered.
...