Web Benchmark recordable actions

Previous Next

A recordable action is an action that you can record in Web Benchmark, or that you can add to a sequence of recorded actions by editing a recording, or both.

Recordable action

Explanation

assert

A test of the value of any modifiable input control. This action can be triggered (ie., added to the test currently being recorded) by clicking such input controls.

 

This action is only used on InputControls. It tests the actual value of an InputControl, independently of its displayed representation, against a given value. It can test whether it is precisely this value (Equals), or not the same as this value (NotSame).

 

The test action differs from the assert action in that:

It is able to test for specific property settings, not just for single values.

Its value must always match: testing the opposite is not possible.

assertEquals

An assert action with Assertion type = Equals.

assertNotSame

An assert action with Assertion type = NotSame.

click

A click on a single element, such as an input field, a title label, a hyperlink, a tab, etc. This is the most generic recordable click action. Clicks on buttons and menus and clicks for data set navigation have their own actions (clickButton, navigateMenu, clickRow).

clickButton

A click on any button except lookup buttons, which have their own action (navigateToLookup).

 

Clicking lookup buttons is special because it involves getting information from the associated InputControl.

clickRow

A click on a non-specified element of a multi-record control. This involves for example clicking on the “white space” of a record in a ReplicatedColumnsControl, or the table cells in a GridControl, without clicking on an actual InputControl of that row.

comment

Currently unused, but can be used to add comments to tests. Has no effect on their execution.

delay

A manually inserted, explicit delay. Used for tests that require explicit delays, e.g. to wait for the ‘Lifetime’ property of a data source to expire.

gotoDataSet

A click on a number item in a DataSetNumbersControl.

invoke

This action provides the usage of subtests by making it possible to call the execution of some subtest from the execution of an embedding (invoking) test. Short frequently used tests can be recorded as normal tests, and then be invoked as subtests.

message

The presentation of a message. This may be a message from the server (Page Engine), or a locally displayed message. This includes developer messages.

navigateMenu

A click on an item in a MenuControl.

navigateToLookup

A click on an InputControl’s lookup button WB_clip0047.

nextDataSet

A click on the WB_clip0048 button of a DataSetNumbersControl.

previousDataSet

A click on the WB_clip0049 button of a DataSetNumbersControl.

script

The execution of a a script, and the test of its result value.

setValue

A value change in any InputControl. The target can be an actual InputControl, but also a field in an input dialog, or a field in dynamically generated HTML or custom controls.

test

A test of the value of a static control (ie., a control that you cannot change by a setValue action). Static controls includes title labels (both of pages and dialog controls), record ranges (TotalNumberOfRecordsControl and RecordRangeControl most specifically), but also the element counts of any select dropdowns. This action can be triggered (ie., added to the teest currently being recorded) by clicking such static controls.

This action can also be used to test for certain property settings (such as for the Updatable property) of InputControls.

The test action differs from the assert action in that:

It is able to test for specific property settings, not just for single values.

Its value must always match: testing the opposite is not possible.