BASE I Business layer

Business-based information is managed in Tosca Commander™. During the test execution an XML file is exported from Tosca Commander™, which serves as engine input and contains the business-based information (see chapter "XML file for engine input").

In the course of the test execution an XML file (Engine output) is generated, which contains the test results and is read by Tosca Commander™ after the test execution (see chapter "XML file with test results (engine output)"). The test results from the XML file are then shown in Tosca Commander™.

XML file for engine input

An XML file always has the following structure:

• A TESTSET element is always the topmost part of the hierarchy. A TESTSET contains all test cases that will be executed.

• Within a TESTSET there are one or several Testcase elements. These testcase elements correspond to the test cases in Tosca Commander™.

• The example above shows one test case with the name New TestCase.

• A testcase contains no or several TestAction elements. A TestAction element corresponds to a module in Tosca Commander™.

• There are no or several ParameterAction elements per TestAction. A ParameterAction element corresponds to an attribute in a module in Tosca Commander™. Only those attributes are listed, which have a value in Tosca Commander™ and which will be executed.

The following example shows a TESTSET named New TestCase. The TestAction name is ETEST. The TESTSET contains two ParameterActions with the ParameterNamesCaption and Text. In the ParameterAction the business-based values (ParameterValues) Heading and Content are stated. The ActionMode is in both cases Input, i.e. these values will be set for the control during test execution. Extract of a TestSet XML file

XML file with test results (engine output)

The XML file for transferring test results to Tosca Commander™ is structured the same way as the Input-XML file. Additionally, this file contains the TestState information, which was generated during the test execution. This information will be placed as separate TESTSTATE tags in those positions where errors occurred.

TESTSTATE tags are only created if an error was detected during the test execution. TESTSTATE information is always saved on the TESTCASE layer, i.e. also in case of a proper test execution (State OK). The duration of the test execution (Duration) is also saved as test result by default.

Objects of the business layer

The information from the above mentioned XML file (chapter "XML file for engine input") is transferred to the business layer of the engine object model. This model reflects the structure of the XML file:

Views on the ParamAction

When the XML file is imported, the ParameterValue is saved in ParamAction.value. The value has to be interpreted depending on the ActionMode:

• Dynamic expressions have to be replaced with precise, current values.

  Example: Use of buffer variables (see chapter "Buffering values")

• Complex expressions are divided into separate parameters.

  Example:"ActionMode Verify".

When the XML value is loaded, the engine provides two different views for every ParamAction, which display the value depending on the action mode used:

• The inputView represents the value for an ActionMode Input. Dynamic expressions are replaced and additional information is extracted.

• The verificationView represents the value for an ActionMode Verify. Dynamic expressions are replaced, attributes, operator and additional information are extracted.