Actions

Actions, as the name suggests, are the actions that you perform to test Application Under Test eg. Opening a URL in the browser, clicking on a button etc. They form the basic building blocks of any test. 

Bq comes pre-packaged with a comprehensive list of actions spanning multiple technologies and covering almost all scenarios that you may come across during testing. If there is ever a scenario which is not already addressed by a built-in action, you can create a Custom Action of your own and use it seamlessly in the test.

Basic construct of an action is as follows:

<ActionName>  <Screen + UI Element>  <Action Parameters>  <Take Screenshot>  <Comments>

Example:

Action Name

Screen + UI Element

Action Parameters

Screenshot

Comments

Action Name

Screen + UI Element

Action Parameters

Screenshot

Comments

SetValue

LoginScreen|userName

BqUser

True

Set "BqUser" in userName field.

Actions are further categorized as :

 

For any action keyword, the keyword will either pass or fail.

There are two kinds of failure for action keywords, in Bq Platform.

  1. Soft Fail
    If the keyword soft fails, the further execution will not be stopped.
    For example, if an incorrect object is provided with the keyword setValue, the keyword will soft fail with the appropriate message & further steps will still be executed.

  2. Hard Fail
    If the keyword hard fails, the execution will be stopped completely.
    For example, for keyword createFile, if a file with the same name and extension already exists at the same location, the keyword will hard fail & further execution will stop.

Â