In this documentation article, learn all about groups and Conditions in Quality Modeller.
Within the rules of each node, there is an expression editor.
This page will consider the following model:
There are three variables, A, B, and C, that can each be assigned with the values 1, 2, and 3.
Upon the ‘Path 1’ task block, we can apply a rule to tailor the generation of paths through the Model. Each node can have multiple groups of Conditions. Groups can be considered as a pair of parentheses in which a condition is contained.
There are a number of examples below that outline how to use the Rules logic, conditions, and groups.
Example 1:
The below rule translates to: A=1 AND B=1 AND C=1
Note that in this case the AND/OR has no impact on the rule logic
Generates the following path:
Example 2:
The below rule translates to (A=1 AND B=1 AND C=1) OR (A=3 AND B=3 AND C=3)
Generates the following paths:
Example 3:
The below rule translates to (A=1) AND (B=1) AND (C=1)
Note that in this case selecting either AND/OR in the blue box has no impact on the rule logic
Generates the following path:
Example 4:
The below rule translates to: (A=1) OR (B=1) OR (C=1)
Generates 19 paths - every single path includes at least one of A=1, B=1, or C=1
Example 5:
The below rule translates to: ((A=1 AND B=1) OR (A=2 AND B=2)) OR ((A=3 AND B=3) OR (A=4 AND B=4))
In plain English, this means that A and B should always take the same value as each other, and all of the variations comes with C as it is unrestricted. Here’s an example test case:
A Condition marks a fork in the paths through a systems logic, for example a decision or a point where data can be entered. To use one, drag it from the Actions panel onto the Model canvas. The Condition itself does not have any decision-making action to decide which paths are followed, use Rules and Tags in the Nodes immediately following the Condition.
Quality Modeller is Curiosity's flow-driven model-based tool which provides a range of accelerators and connectors for building flowcharts rapidly. Align all stakeholders to quality outcomes and create critical assets early, delivering superior software at speed.
A Model is a canvas and the Flow that is built onto it. There are several types of Model, some of which display different tabs and tools on the toolbar in Quality Modeller.
A Condition marks a fork in the paths through a systems logic, for example a decision or a point where data can be entered. To use one, drag it from the Actions panel onto the Model canvas. The Condition itself does not have any decision-making action to decide which paths are followed, use Rules and Tags in the Nodes immediately following the Condition.
Rules are conditions placed on Model Nodes of a Non-Linear Model that control whether the processing of a Flow passes through that branch. The Rules tool can be found on the Test Generation tab. When a Rule has been applied, a Rules logo appears in the Node were the rule was applied, and when that Node is selected, number appears next to the Rules button to show how many Rules have been applied on that Node.
This website uses analytics cookies. These cookies are used to improve your website experience and provide more personalized services to you. To find out more about the cookies we use, see our Privacy Policy.