Page History

Keeping in mind that our integration capabilities are constantly evolving, we can consider the following simplified toolchain as the status quo for this discussion:

Note: some of the specific tools around Enterprise Test Case Designer in the image above are mentioned for example purposes and do not represent the exhaustive list.

Let’s look at both integration sides from Enterprise Test Case Designer perspective in more detail.

Left Side

The first part is to include traceability notes inside the Enterprise 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).

...

These steps reduce redundancy risk across the test suite given common one-to-many relationships between tests and requirements.

Left Side – how is “Best Practice” different?

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 Designer.

...

Potential improvement #4: Add “Enterprise 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.

Right Side

The primary method is exporting from Enterprise Designer into compatible CSV and importing into test management tools (like Xray). Enterprise 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 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).

...