Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

1. TCD models can be shared at the project level by separately including email addresses or sharing the secret link with the group. You can choose one of 3 permission levels for each colleague. If you do not want some models to be seen, you can move them from the project state to the private one by editing in the “Your Test Models” dialog.

...


Once you have created the optimal model and confirmed it with the stakeholders, it is time to move the test suite to execution. Many of the downstream actions are typically performed in test management tools (e.g., Xray) or in automation frameworks (e.g., Ranorex Studio). We will focus on the steps that have a direct impact on the Test Case Designer models.

...

To clarify, freezing makes the italicized values (red rectangle highlight highlighted above) constant by saving all scenarios as Forced Interactions. Italic type means that TCD has already covered all n-way interactions for that parameter and now randomly selects a value from the available list. Therefore, without freezing, there is a chance the value will change on suite re-generation. This could pose a challenge with test data preparation if, for example, distinct accounts need to must be set up to represent each of the scenariosscenario.

Ongoing maintenance

While we recommend unfreezing the test suite before incorporating new information into the model, in some cases, the updates can be made on top of the preserved scenarios. You have to keep in mind remember that frozen test cases will often prevent TCD from finding the most efficient way of including changes, which leads to the avoidable growth of the test suite.

We will focus on the situation where the test suite can be re-generated completely. Regarding sources of information, new requirements are the one ones mentioned most often, but you should not overlook execution and defect reports. While TCD does not execute your tests, establishing the feedback loop and ensuring your TCD model includes the interactions that have caused issues in the system is critical for the long-term value of the tool.

...

  • To avoid unnecessary complications when you just want to rename an individual Value, we recommend that you do that by clicking on the actual Value, not on the parameter name.


  • Adding or removing values can be done via Edit, Bulk Edit, or Mind Map modes – depending on the number and format of changes.
  • Within Auto-scripts, you can edit the content of each step and its position in the overall script by hovering over and clicking the pencil/arrow icons:


Complex Changes

We will take a look at 2 examples: significant updates to the constraint logic and merging ideas from multiple models.

Example 1: When the input set is constant, and the constraint logic is changingchanges, you have to either delete relevant constraints 1-by-1 or, if the updates are drastic, bulk delete them and start from scratch.

  • You can leverage the browser search to identify constraints for the necessary values:


When the parameter set is changing changes and that affects the constraint logic, the warnings will appear as you adjust the content on the first TCD tab. Please read through the impacted constraints and make sure ensure the change you are making is the correct & efficient one. If you see a banner appear about “No possible values”values,refer to another article in this category.

...

Info
Parameter lookup works at the project level.


  • You can add constraints via copy-paste in Advanced Mode
  • Depending on the elements of each model, it may be more efficient to merge 3 exports in Excel and create a new model from Excel import:

...

Info
If you are dealing with the integration testing, we often recommend decreasing the level of detail – in other words, do not merge all parameters & values from multiple models, but instead reevaluate which are the crucial ones from the integration perspective and abstract the rest.