Reference › Test Case Reference › Assertion Descriptions › Other Assertions › Highlight Text Content for Comparison

Highlight Text Content for Comparison

The Highlight Text Content for Comparison assertion uses the "paint the screen" technique that was designed to work with HTML pages. For example, if there is a large HTML document, you identify the data before and after the content of interest. Then, you simply identify what to compare the "content of interest" against (typically an expected value that is supplied in a data set).

The text is marked using the icons at the bottom of the editor:

This technique is best explained by using an example.

In the following example, we want to complete the following actions:

• Ensure that specific files appear in the buffer
• Compare one of the file sizes to the value of a property

The text is marked using the three icons that are shown in the previous graphic, by selecting text and clicking the appropriate icon.

• Yellow background indicates text that must appear exactly as shown.
• White background indicates text that does not need to be present, or can change.
• Red background identifies the text that must match the property that was entered into the dialog.

  

The set of tokens that is shown here can be read this way:

• The buffer must start with the phrase in yellow: "Snapshot of: C:\Lisa\".
• The number of files in the buffer in the next token can vary. Because the token is an "Any" token, the variance is immaterial.
• The file "i4jinst.dll" and "rw" attributes must appear.
• The red filesize means that the value associated with the property key filesize are swapped into the expression, then the comparison made.
• The text "06/08/2011" must appear.
• The file "install.prop" must appear.
• The buffer can have any amount of content afterward.

After you have finished the markup, enter the following parameters:

Name

Defines the name of the assertion.

If

Specifies the behavior of the assertion from the drop-down list.

then

Specifies the step to which to redirect if the assertion fires.

Log

Identifies event text to print if the assertion fires.

Click Run Assertion to execute the assertion.

Note: "Must" blocks must always appear on both sides of "Property" blocks.