Rules allow you to force the path generator down paths that contain particular data values (outputs), while excluding others. They thereby provide a way to filter test cases when generating a test suite.
Why use rules
Rules allow you to overlay constraints onto the model, quickly generating different combinations of paths. This provides a fast alternative when modelling out the full logic for each set of scenarios would be cumbersome.
With rules and coverage profiles, Test Modeller can generate accurate tests for complex systems. Yet, the flowcharts their simplicity and usability. This is because rules provide a compact alternative to modelling out the full business logic as flowcharts.
Rules leverage coverage profiles to generate paths that include certain nodes. These blocks have rules assigned to them, containing particular values. Path generation using rules then generates paths that pass-through nodes that contain particular values in their rules. This overrides any nodes test data value assigned to that block.
To filter based on these values, a variable is set at the model-level. This model-level variable is then included in the rules and associated coverage profile. This variable creates a filter, allowing you to filter by test data values contained in the model rules. The filter uses Boolean logic. Paths that contain the specified values in their rules will then be included or excluded from the paths generated using that coverage profile.
There are therefore two types of variables involved in Test Modeller. Each serves a different purpose:
A "model-level variable" used in rules and coverage profiles. This rule filters path generation based on values assigned to certain nodes/blocks.
"Test data variables" used to assign values to blocks at the model. These variables are used to define the outputs (values) of decision gates in the model. The values reflect the different logical journeys that a user or data can pass through a system.
You should keep these two types of variables separate in your understanding and practice. Do not use a variable to assign test data values to blocks at the model level and also to filter paths during generation. This risks creating ambiguity in the Boolean logic used to filter paths based on test data values.
It is best practice to name the model-level variable intuitively, for instance, naming it "Path type". This makes it clear that it is not a variable used to assign test data outputs to blocks, but rather that is used to filter based on test data outputs.
The process for rule-based test generation is as follows for an individual model:
Identify relevant decision gates in your model. A 'relevant decision gate' is one with which you want to filter paths based on its outputs.
Create a model-level variable with which to filter paths.
Create rules for every node (output) in the relevant decision gate. The rule informs the path generator when it should include paths that pass through the node, based on data Values set in the rule. The rule use the variable created in step 2.
Create a coverage profile to filter paths based on the test data values. This coverage profile will generate paths that pass-through blocks with certain values contained in their rule. It uses the model-level variable created in step 2.
Generate test cases from the model. This will force the test generation engine down the paths with values included by the rules and coverage profile.
The true value of using rules is realised when subflows are used. This enables accurate integrated test and data generation. You can link subflows in master models, generating paths that take certain end-to-end routes through the modelled logic. This requires the following additional steps:
Embed a subflow for which rules have been defined in a master model.
Create a model-level variable in the master flow. This calls particular test data variables the subflows, filtering paths based on the values assigned in rules at the subflow level.
Create a coverage profile that will filter paths based on the values associated with the test data variables specified in #6.
The links in the above list provide complete articles on creating test data variables, tagging values and generating tests. The following two articles focus on using test data variables to inform rules. They provide instructions on creating rules and coverage profiles for rule-based generation. The first article sets out how to use rules within an individual model (steps 1-5 above). The second provides instructions on uses rules with subflows (steps 6-8).
TEST MODELLER TEST CASE GENERATION