Relevant for Power Mode only
During a test run with mirroring, you may want to periodically compare the display of your primary machine with those of your secondary machines. When you compare the displays, Sprinter detects differences between the displays.
Once you resolve the difference between the displays, you may want Sprinter to ignore similar differences in the future.
When you create a rule, you teach Sprinter to ignore certain types of differences during a compare operation.
Rules are associated with a specific application, and are available for all tests that are configured to use that application. You can also create rules that apply to all your Sprinter tests, regardless of their configured application.
When you create a rule in the Differences Viewer, Sprinter automatically re-compares the secondary machine with the primary machine, to determine if the difference is no longer detected.
Sprinter provides you with a set of built-in rules that address the most common differences that can occur between machines. These rules tell Sprinter to ignore differences up to a certain amount, in the position, size, and location of objects in your display. By default, Sprinter will not detect differences between displays, that meet these rules. Built-in rules apply to all your Sprinter tests, regardless of their configured application.
For more details on these rules and how to enable, disable, and configure them, see Mirroring Settings Pane (Settings Dialog Box).
When you view a difference in the Differences Viewer, you have the option to create a new rule to resolve the difference. When you create a new rule, Sprinter gives you the option to select from a set of pre-defined rules or to create a custom rule.
A pre-defined rule teaches Sprinter to ignore the same type of difference in the future. For example, if the difference is that an object is present in one display and missing in another, a pre-defined rule would ignore the missing object in the future.
If the difference is that a property value of an object is different between machines, the pre-defined rule would ignore that property value in the future.
For details on the specific options available when you select a pre-defined rule, see New Rule Dialog Box.
If a pre-defined rule does not meet your needs, you can create a custom rule.
You create a custom rule using the Rule Wizard. The rule wizard gives you control over the following aspects of a rule:
Type. The type determines whether the rule will ignore a specific object, a property of a specific object, but not the entire object, or a property of all objects. When you define the rule type you do not define which object or object property will be ignored, only what type of action the rule will take.
Scope. The scope determines when the rule will apply. You can choose to have the rule apply to the currently configured application, or to all applications. Applying the rule to all applications means that the rule will apply whenever you run a test in Sprinter with mirroring.
Target. The target is the object to which the rule will apply. If your rule Type ignores a specific object property, the object you select determines which properties are available to ignore.
Action. The action determines the specific action the rule will take when it is applied. If your rule Type ignores an object, the action will be to ignore the object. If, however, your rule Type ignores a specific property, the action enables you to select the specific properties you want to ignore. The properties you can ignore will be the properties associated with your Target object.
Condition. The condition determines the specific conditions under which the rule will apply.
The condition does not have to depend on the property value you want to ignore.
For example: Suppose you create a rule to ignore the color of a button. But you know that the color will only be different when the text in the button displays
OK instead of
Yes. You want to ignore the color of the button, but when you want to ignore the color depends on the text in the button.
You can create a rule to ignore the value of the Color property, and then set the condition for the rule so that it applies only when the Text value is
It is not necessary to set a condition for a rule. If you do not set a specific condition for a rule, the rule will apply whenever the property value you selected for the rule is different between machines.
When Sprinter detects differences between machines, it sometimes combines multiple differences into one difference to simplify the displayed information.
Suppose Sprinter detects a difference between two machines, where one machine displays a table and the other does not. In this case, Sprinter will list the missing table as a difference in the Differences Viewer, but will not list each individual cell within the table as a difference.
When you create a rule to resolve a difference, Sprinter recompares the two displays to apply the new rule and remove the difference from the list of detected differences.
When Sprinter applies a rule to a difference that combined many differences and removes it, the individual differences it combined are now detected separately.
In the above example, when you create a rule to ignore the difference of the missing table between the two machines, Sprinter recompares the machines to apply the new rule and removes the missing table from the list of differences. Once the missing table is no longer detected, Sprinter detects all the individual cells within the table as differences between the machines.
In this case, when you create a rule to resolve a difference, you may see new differences appear in the Differences Viewer. You need to create a rule for each of these newly detected differences as well. Sprinter may detect multiple differences for Web objects as well, such as browser, page, and frame objects in the same window.