Action Logic Editor is central to ACCELQ's codeless test logic development capabilities. It provides various tools necessary to build and manage Action logic. Logic can be built either using recorded UI Views or by directly typing the statement in the editor.
Action logic editor comprises of following sections. Subsequent articles in this section provide further details on these capabilities.
Action toolbar includes buttons to accomplish following tasks:
- Check-out/Check-in if version control is enabled
- Clone Action
- Locally execute the Action
- Delete Action
- Refresh Action
- Insert API statements
- Find References to this Action
This is where the logic is displayed in natural English format. Each line displayed in the Editor is a Statement, which can be generated through multiple interactions. Once the logic is created, you can edit various aspects such as parameter values, capturing return values, comment/uncomment, inserting annotations etc. in the editor.
View Canvas displays all the Views captured for the Context in which the current Action is defined. You can select one of the Views and start interaction. By hovering on different elements on the Screen, you can also create statements for UI interactions/verifications.
Information sidebar allows you to view/edit basic configuration information of the Action including name, description, Origin Context, Destination Context etc. In addition, you can also set values for custom fields from the sidebar.
Action logic allows parameterization to replace hard coded test data with variable data from a Scenario/Test Case. An Action may also output certain information by populating Output Parameters in the logic. In addition, during the logic development, you may also create Local Parameters to store/retrieve information private to this Action.
Parameters are displayed in the sidebar in Action Logic Editor. You can edit/manage all parameter types from here including the local parameters.
Your test logic may comprise of statements interacting/verifying UI fields. Element Repository lists down all such elements of interest. You can manage the definition of elements from this repository. In ACCELQ, elements are centralized for a given Context. That means, all Actions defined in a Context share the same repository.
An Action can be shared with other Contexts, so that it can be used in a Scenario from various places. You can edit/manage sharing attributes from here.