| AFP GUI |
The Avaloq Front Platform Graphical User Interface (web interface) that AST can test for expected interaction. |
| AMI |
Avaloq Messaging Interface. AST uses this interface to send and process messages, simulating an external system and bypassing the Avaloq MQ Bridge. |
| Annotations |
XML elements used to define meta information for test cases, such as categorization and labeling (e.g., "Stage", "Kind", "Domain"). They do not affect execution but are included in reports. |
| Arguments |
Placeholders in an XML test script that correspond to column names in an external data sheet (e.g., Excel). They are populated with test data at runtime and behave identically to variables. |
| AST Core (Testing Module) |
The test execution engine component of the AST Suite responsible for running test cases, verifying results, and generating reports. |
| AST Control Panel |
The user-friendly web interface component of the AST Suite for managing test cases, scheduling executions, viewing analytics, and administering users. |
| AST Expression (AstExpr) |
A type that can use a static string or a combination of multiple variables ({$var_name}) and static text. Variables are replaced with their runtime string values and concatenated with the static text. |
| AST Suite |
The comprehensive platform consisting of two main components: the AST Core (the execution engine) and the AST Control Panel (the web interface). |
| Avaloq Open Interface |
The standard interfaces (DDIC, Report Writer, AMI, etc.) used by AST to connect to and communicate with the Avaloq Banking System. |
| AvqExpr (Avaloq Expression) |
An expression used in the AST test XML to define an Avaloq scripting expression. It dynamically substitutes prefixed variables ($var_name) with their runtime values (removing any leading #) before the script is executed by the Avaloq connection. |
| Control Statements |
Tags used to manage the flow of a test run or define specific settings, such as <if>, <select>, <wait>, and <session>. |
| Coverage Analysis |
An automated process executed and reported for every test run to measure the extent of test coverage. |
<debug> |
An XML tag used to display a customizable text message or the current value of one or more variables ({$variableName}) in the log for troubleshooting, but only if the system setting ast.base.debug is set to true. |
| DDIC |
Data Dictionary. It defines the properties and fields of business types, which AST uses to set properties in operations like <new-doc>. |
<doc> |
An XML Operation used to process an existing order by identifying the specific order (by its ID or key) and executing a specified workflow action. |
| Execution ID |
A unique identifier generated by the AST Control Panel that tracks a single test run or scheduled execution across its entire lifecycle, particularly when interfacing via REST APIs. |
| Input Operations |
A category of functional elements (operations) used to modify the test object (the Avaloq system) by performing actions such as creating an order (new-doc), processing a file, or executing a task. |
| Input Step |
A high-level Test Step that logically groups Input Operations (e.g., <new-doc>, <file>) used to modify the state of the Avaloq Banking System or the test object. |
| Methods |
Reusable blocks of test script functionality often used to implement common sub-steps. They are stored in separate XML files and can be invoked using the <invoke-method> tag. |
<new-doc> |
An XML Operation used to create a new order in the Avaloq Banking System, supporting all interactions a user would perform in the graphical user interface. It requires an initial workflow action (init-action) and a closing workflow action (close-action). |
| Operation |
The basic functional element that corresponds to a base functionality of the Avaloq Banking System. Operations are grouped to form a Test Step. |
| Query Operations |
A category of functional elements (operations) used to perform read-only access to retrieve information from the test object, such as checking the status of an object, order, or message. |
| Query Step |
A high-level Test Step that logically groups Query Operations (e.g., <obj>, <doc>) used for read-only access to retrieve information from the Avaloq system. |
| Scenarios |
XML-based containers that define groups of test cases and their execution dependencies. They enable test flows where one test case utilizes the results of a preceding one. |
| Scriptlets |
A parameter within <doc> and <new-doc> operations that allows the direct integration of Avaloq Script code into the order generation process. |
| Test Case |
A comprehensive Avaloq business case defined in XML format to be tested automatically. It consists of one or more sequential Test Steps (Input, Query, Verify). |
| Test Data |
The business-specific values used to drive a test case. It's rigidly separated from the Test Logic and typically defined by business users in Excel files. |
| Test Script / Test Logic |
The implementation of the business case logic, defined by specialists using the XML-based Test Script Syntax. It is rigidly separated from Test Data. |
| Test Set |
A logical group or suite used to organize multiple test cases for streamlined execution. They are managed via the Sets menu in the AST Control Panel. |
| Test Step |
The fundamental middle layer in the test execution hierarchy, organizing a sequence of Operations. The primary categories are Input, Query, and Verify. |
| Variables |
Elements defined using the <variable> tag that allow information (values) to be shared and passed between different operations and steps within a single test case. |
| Verify Operations |
A category of functional elements (operations) used to test for specific conditions, such as comparing values, checking financial bookings, and verifying message content. The outcome is reported as either a success or a failure. |
| XML-based Test Script Syntax |
The simple, proprietary language used by specialists to define the Test Logic (scripts) for the AST Core. |