Available Core Steps

This is the syntax documentation for the Core steps.

The webtest task includes all information about a test specification. It contains the optional nested tasks config which defines configuration information and steps which defines a sequence of test steps.

The webtest and steps elements can contain any number of ant or webtest tasks.

The main Core steps provide the ability to invoke pages, store values, and verify various information about visited pages. Examples include: invoke clickLink clickButton followFrame previousResponse setCheckbox setInputField setRadioButton setSelectField storeCookie storeRegEx storeProperty storeURLEncoded storeXPath storeHeader verifyCookie verifyElement verifyInputField verifyTitle verifyText verifyTextarea verifyProperty verifyLinks verifyXPath

Test steps can be further grouped (and even nested) using the following steps: group not repeat ifStep timedGroup retry

In addition, there are special steps which help set appropriate context information, e.g. selectForm can be used to select a particular form as the current form and verifyText can contain the table locating step.

Most of the steps work on the "current page" (actions like clickLink, clickButton, ... as well as verifications like verifyTitle, verifyInputField, ...). The notion of "current page" is quite simple when no JavaScript is involved: it is the result of the last action step triggering a request (invoke, clickLink or clickButton) or the frame followed by followFrame or the response restored by previousResponse. It becomes more complicated when JavaScript is involved but it aims to be as "natural" as possible. A newly loaded page becomes the new "current response" if one of the following conditions applies:

the page is loaded in the window of the current response

the page is loaded in a new window

the page is loaded in a frame which enclosing page is already loaded and the load was not triggered by JavaScript

Furthermore if the window containing the "current response" is closed, then the content of the last opened window becomes the "current response".

Proxy settings configured with the ant <setproxy> task prior to webtest are used to access the website to test.