Page History
...
To do so, it carefully constructs combinations of test conditions con ditions to achieve as much coverage as possible in as few tests as possible using applied statistics-based optimization methods that have been refined over more than 40 years.
...
Terms & Concepts
Test Model
A Test Model is your test bench where you define all the parameters, values and rules so that the system can generate all the scenarios and test scripts automatically. In this section we will go through the basic steps to create/copy your test models.
Parameters
is an abstraction of a focused use case that we aim to test. This model is made around a specific scope (e.g., "book a flight") that can be exercised in different ways, depending on a combination of input paramteters (e.g., "origin, destination, number of seats, date"). To find bugs related with the input parameters and increase the related coverage, an optimized set test cases (manual or automated) can be derived from it.
Parameters
The parameters are used to define the variables, and the related possible values, that are applicable to the Test Model. Usually these refer to the input variables.
Parameters, together with the restrictions specified using Rules, will be used to derive the combination of parameter/values.
More info on Parameters 
here.
| Info |
|---|
| Test parameterization is a powerful practice that allows the same test to be executed multiple times with different parameters. Parameters are similar to input values (variables) that can change with each execution. |
Rules
While Parameters are used to enumerate, in general, the variables in our Test Model and the values they can have, Rules allow us to apply some restrictions as we may not be interested in having all the combinations of these variables.
Rules can be used to define In specific scenarios, system allows user to define what parameter values can never be tested together, as they either don't make sense in reality (e.g., Windows + Safari) or because they may not be representative/relevant.
In or in the other hand, Rules can also be used to enforce scenarios where parameter values can only be tested together.
These are called rules and you can find more information here
Scenarios
The core process where user can define using powerful coverage optimization algorithms and multiple combinatorial strengths to achieve greater coverage in fewer overall tests.
Scripts
More info on Rules here.
Scenarios
Scenarios are the generated combination of input parameter values, where each row represents a combination of parameters (and their values) to be used in a test.
We can think of Scenarios as an optimized dataset that will be used to iterate our Test Model multiple times, and thus test it under slightly different circumstances.
Not all combinations of parameter/values are created. Test Case Designer uses coverage optimization algorithms (pairwise, n-wise) to achieve an high level of coverage with in few tests. This can be adjusted toachieve a greater coverage if needed.
Scripts
While Scenarios focus on data that will be used for our tests, Scripts provide the actual context so that testers know how/where to apply it.
Scripts have the detailed steps with actions and expectations for our test scenarions.
Scripts can be either manual test scripts or automated test scripts.
For manual test scripts, detailed steps and expected results can be specified, where parameters may be mentioned. These will be replaced by the respective values whenever generating the tests later on.
For automated test scripts, Gherkin (e.g., Cucumber) Scenario or Scenario Outline can be specified or even Robot Framework test cases. Similarly to manual test scripts, parameters can be mentioned in the specification, so they can be replaced later on by proper values.Scripts are user-assisted tests, listing an assortment of guidelines the user must follow, and the results that such behavior is expected to accomplish.