BASE I Engine object model

Each TestCase execution needs three types of information:

1. Business-based information about the content of the TestCase and the test data (see chapter "BASE I Business layer").

2. Definition information about the logical control type used for steering a particular screen element (see chapter "BASE I Definition layer").

3. The current technical values of the screen element to be steered, such as table content, field positions, etc. (see chapter "BASE I Representation layer").

Example

The illustration below shows the layers of the Engine Object Model for steering ComboBoxes in HTML/web applications:

• The business-based information about steering is located in the category ParamAction (see chapter "Objects of the business layer").

  Which element should be selected?

• The definition information is stored in the class ControlDef (see chapter "Tags of the definition layer in the XML file (ObjectMap)").

  The screen contains a ComboBox named year of manufacture which is technically identified using HTMLId=cbyearofmanufacture.

• The technical information of the control in the application is available for the engine in the class HTMLComboBox.

  The currently selected item 2005 is active (enabled).

HTMLComboBox is a class derived from PARep. PARep is a predecessor for all specific control types (see chapter "Tags of the definition layer in the XML file (ObjectMap)").

• The HTMLComboBox contains access and steering information for the ComboBox in the test object and is no longer part of Tosca Base Engine.

• The HTMLComboBox is part of Tosca HTML Engine.