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 nested tasks config (soon to be optional) which defines configuration information and steps (soon to be optional) which defines a sequence of test steps.
The steps element can contain any number of Core, Extension, PDF or grouping test steps. A recent feature is that you can also mix in normal ANT tasks as well. You can use the antWrapper step or just add them in and an antWrapper step will be added implicitly for you. This is fairly new and hasn't had extensive testing yet - use with caution.
The main Core steps provide the ability to invoke pages, store and verify various information about visited pages, and manipulate HTML forms and include: invoke clickLink clickButton followFrame previousResponse verifyTitle verifyText verifyElement verifyElementText verifyTextarea verifyInputField verifySelectField verifyLinks verifyXPath verifyCheckbox verifyCookie setCheckbox setInputField setRadioButton setSelectField storeRegEx storeProperty storeXPath storeDynamicProperty storeCookie storeHeader verifyProperty
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.
- the page is loaded in the window of the current response
- the page is loaded in a new window
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.