Reference › Test Case Reference › Assertion Descriptions › XML Assertions › Highlight Text for Comparison

Highlight Text for Comparison

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

Mark the text with the icons at the bottom of the editor:

In the following example, we want to:

• Ensure that the buffer contains specific files
• Compare the size of one of the files to the value of a property

We have marked the text using the three icons that were shown in the previous graphic, by selecting text, and then 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 is entered into the dialog.

  

The set of tokens that is shown in the previous graphic can be read this way:

• The buffer must start with the phrase in yellow: "Snapshot of: C:\Lisa\".
• A number of files may or may not be in the buffer in the next token. Because the next 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 is swapped into the expression, and 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.