# Terms and Definitions

<table data-full-width="true"><thead><tr><th width="179">Term</th><th>Definition</th></tr></thead><tbody><tr><td>About</td><td>Contains the release and license information of OMrun.</td></tr><tr><td>Batch</td><td>System call to execute a OMrun runtime instance, which publishs results to the [OMdashboard] and exports the [List of Differences] to Excel.</td></tr><tr><td>Breadcrumb</td><td>Shows the icons of the selected and active elements for execution in a "breadcrumb".</td></tr><tr><td>Business rule</td><td>Represents the relation mapping between source A and B specified in rules with SQL commands.</td></tr><tr><td>Business system</td><td>Describes the complete system landscape of all environment definitions and valid test elements.</td></tr><tr><td>Component</td><td>Container to group [Test object] that are of a similar behaviour. Containers are visible on OMdashboard.</td></tr><tr><td>Configuration</td><td>Contains the data and program adapters as well as the publishing definitions for the scenarios represented on OMdashboard.</td></tr><tr><td>Data adapter</td><td>Describes the database connect string using a specific data adapters within the OMrun configuration to connect to almost every commercial data container.</td></tr><tr><td>Global environment</td><td>Contains the environment definitions which are valid for all environments defined within the same [Business System].</td></tr><tr><td>License</td><td>Contains the license key to run OMrun as a Full-Version or a RunTime-Version or both.</td></tr><tr><td>List of differences</td><td>Excel result list containing the differences from source A and B created by a [Batch] run.</td></tr><tr><td>Local environment</td><td>Contains the environment definitions for a specific environment, like "environment name", "server name", "date base name" etc.</td></tr><tr><td>OMdashboard</td><td>Web management dashboard to present an overview of the last test results aggregated to a wider audience as ample lists and pie chart diagram as well as historised result performance.</td></tr><tr><td>Parameter</td><td>Variables defined within a [Parameter list] are possible to use within [Queries] or [Business rules].</td></tr><tr><td>Parameter list</td><td>Container for a list of [Parameters] defined specifically for a [Test object].</td></tr><tr><td>Post-condition</td><td>To set condition after comparing data and generating results (e.g. cleansing old data, archive last results, etc.).</td></tr><tr><td>Pre-condition</td><td>To set the condition needed before running a proper data compare (e.g. reset test data record within the database, execute a calculation, etc.).</td></tr><tr><td>Program adapter</td><td>Describes the program connect string within the OMrun configuration to connect to several standard test tool products, programs or [Batches].</td></tr><tr><td>Progress bar</td><td>Shows the progress and the current task of a test run executing a [Scenario], [Parameter list] or [Test object] as progress bar.</td></tr><tr><td>Query</td><td>SQL statement to gather data from a specified source (A or B).</td></tr><tr><td>Result export</td><td>Export of the [Results] as an Excel sheet.</td></tr><tr><td>Result history</td><td>Mechanism to reload [Results] from previous test runs.</td></tr><tr><td>Results</td><td>Statistical reports or [Lists of differences] generated by [Scenario], [Parameter list] or [Test object] execution.</td></tr><tr><td>Scenario</td><td>Workflow-Engine (step-by-step) scenario execution, executes all [Test object] entries with the specified [Parameter list].</td></tr><tr><td>Test data object</td><td>Test data object is the essential element of a data compare. It contains the [Queries] for source A and B, the [Business Rules] to represent the relation between the data to compare and the parameter list to feed the [Queries] with different values in [Variables].</td></tr><tr><td>Test object</td><td>Test object is the parent term that describes [Test data objects] and [Test program objects].</td></tr><tr><td>Test program object</td><td>Test program object is the essential element of a [Scenario] execution. It enables the system to add [Pre-Condition] or [Post-Condition] for highly automated [Scenario] runs.</td></tr><tr><td>Tree</td><td>Representation of the whole content of the [Business system] as a tree structure.</td></tr></tbody></table>