Core Step verifyText

Description

This step verifies the existence of the specified string somewhere in the response received from server (ie the changes that may have occured since the page has been loaded are not seen by this step). The text could represent an HTML fragment like "<BODY>" or a arbitrary static text in the page ("An application error has occurred!").

Parameters

text: Required? yes; The text value to verify against.
description: Required? no; The description of this test step.
regex: Required? no, default is 'false'; Specifies whether the text value represents a regular expression.

Inline Text

The inline text is all the text between the start tag ( <verifyText> ) and the end tag ( </verifyText> ), including blanks, tabs or newlines. Using a pair of start/end tags ( <verifyText> </verifyText> ) has not the same behavior than the seemingly equivalent empty element tag ( <verifyText/> ).

Required? no

Alternative way to set the 'text' attribute.

Nested Parameters

table: Required? no; To locate a specific cell in a specific table on the page.

Details

verifyText example1

verifyText example2

<webtest name="Check body tags">
  <config ... />
  <steps>
    <invoke ... />
    <verifyText description="Checks for the existence of HTML body tags"
      text="<BODY>.*</BODY>"
      regex="true" />
    ...
    <not description="the word 'error' should not appear in the page">
      <verifyText description="search for the word 'error', case insensitiv"
        text="(?i:error)"
        regex="true" />
    </not>
    ...
    </steps>
</webtest>