Open Test Framework  
Introduction

The OTX development environment Open Test Framework (OTF) supports the user in all tasks related to OTX. The following use cases are in the foreground:

Use Cases:

  1. Representation
    The test logic is represented graphically and textually so that it can be intuitively understood by different target groups such as developers, integrators, testers, specifiers and managers.
  2. Editing
    The test logic can be edited with all OTX details in the graphic designer or for developers in the OTL editor. The user is supported by numerous assistants, which make input safer and more productive.
  3. Validation
    Using standardized and extended checker rules, the test logic is checked for standard conformity and semantic correctness as soon as it is entered. The diagnostic validation checks the correct link to the ODX diagnostic database.
  4. Software Testing
    With the help of unit tests written in OTX, the test logic can be protect against the expected behavior.
  5. Conversion
    For execution, the test logic described in OTX is converted into an extremely fast and resource-saving runtime format, which can also executed in embedded systems.
  6. Debugging
    In order to analyze the runtime behavior, the OTX test logic can be executed completely or in single-step operation.
  7. Export
    For distribution, the OTX files are exported to the standardized PTX container format.
  8. Profiling
    The OTX runtime can generate profiling files at runtime. The runtime behavior on the target system can thus be analyzed inside the profiler.
  9. Utility Support
    Numerous utilities related to the use of OTX in the process, such as OTX mapping editor, proxy editor, procedure call editor, sequence designer, etc. are available.

Further Topics:

The OTF mainly consists of the following components:

  • The Solution Explorer is the central entry point to OTX and displays the OTX structure at the file system.
  • The Declaration Window lists all local and global parameters, variables and constants and allows them to be edited.
  • The Designer Overview presents a reduced view of the graphical OTX workflow for navigating it.
  • The Property Grid lists all properties of the selected element and allows them to be edited.
  • The Status Bar provides an overview of the current status and diagnostic configuration.
  • The Variable Trace window lists every change to a variable at runtime.
  • The Communication Trace window also provides a detailed display of all diagnostic request and response messages during runtime.
  • Various Output Windows clearly display errors or warnings, watch declarations for single-step operation (debugging) or show the XML raw representation of OTX.
  • The Toolbox on the left lists all activities grouped by different extensions.
  • The actual OTX procedure with its parameters is located in the middle.
  • At the top is the Office-style Menu Bar for quick access to frequently used functions.
  • The Workflow Designer graphically represents the test logic in the form of an activity diagram and
  • The activities contain all parametrizable OTX Actions and OTX Terms as OTX core elements.
  • Besides the graphical designer the OTX test logic can be also created via OTL Code Editor.