TableDrivenBlock Editor-Table Editor/en

Table driven test editor

The following document describes the table driven test editor. The table driven test editor can be used for tests with a sequential test flow.

If tests get more complex table driven blocks can be transformed to compound blocks.

Toolbar

In the left function group of the toolbar you will find the buttons concerning the test execution.

• Start a test run (of the edited Block only) or continue after a breakpoint or execution pause. This allows for a changed block's functionality to be checked immediately, without a need to create an extra compound block or a testplan-item for it to be executed. If the edited block needs input values or other prerequisite setup for the test run, these should be defined in the tab named "Test/Demo" (which is the rightmost tab of the editor).

• Start a test run but open a debugger window in case of test failure, even if the debugger is currently disabled in the settings. This kind of run is helpful during test development or error analysis. It enables debugging mode without changing the settings.

In the right area of the toolbar you will find the following functions concerning the presentation.

• Collapse all step items. All In- and Output pins of a step are hidden.
• Expand all step items. All In- and Outpur pins of a step are visible.

Tasks

Adding Steps

There are two possibilities to add new entries so called steps to the table; via drag & drop from the project tree or by using the conext menu selecting <New Step>. The step is initially selected, indicated by the highlited row. The inputs of the new created steps are set to its default value dependent on the setting...

Selecting Steps

Steps can be selected by left-clicking on it. Additional steps are selected by holding down the Shift-key in conjunction to the left mouse button. In a similar way, pressing the Control-key (CTRL or STRG) toggles steps into or out of the selection.

Another possibility to select multiple steps at a time is to mark a selection rectangle area with the mouse, which selects all steps (and other elements) that are within that area.

Arranging Steps

To arrange steps you can move rows up and down in the table, replace steps and remove them via the context menu. Since tables represent a sequential test flow you reorganize the execution order by arranging steps.

Indicators

• The step has the auto exec option flag set. The step will start even without a triggering input. This flag is required for steps of which all pins are non-triggering (for example, because they are "frozen" to fix values), or to steps which have no input pin at all.

• Shown for skipped steps. Skipping steps is often useful during test-development, to skip over either unfinished actions, or when proceeding development after a change, to skip over already executed steps. When the test goes into production, however, all skip-flags should be removed.

• Shown for steps which fork a new activity for every incoming set of values. If this flag is not set, incoming values are remembered in the step's input baskets, and will be processed sequentially. Notice that in releases prior to 1.9, the default execution mode was "parallel" and the user had to change this to "sequential" via an explicit menu action. Starting with 1.9, the default when placing new steps is now "sequential". Therefore, when you load old test-suites into a post-1.9 expecco editor, you will see these indicators all over the place.

• Shown for steps which ignore exceptions.

• Shown for steps which are not traced in the activity log.

• The step has a breakpoint set. When reached during a test run, the executir will pause and wait for either the "Run/Continue" or the "Single-Step" button tp be pressed.

Menu

Main Menu

Common Options

This menu can be found as diagramm in the main menu:

• Aspect
  Txt.

• Refactor
  Txt.

• Import from CSV file ...
  Txt.

• Environment...
  Txt.

Common Options (Context Menu)

Common Options

When nothing is selected in the editor:

• New Step
  Txt.

• Goto
  Txt.

• Search, Next and Previous
  Txt.

• Aspect
  Txt.

Step Specific Options (Context Menu)

Step Specific Options

When a step is selected in the editor:

• Copy, Paste and Delete
  Txt.

• Open Editor
  Txt.

• Open Browserpage
  Txt.

• Goto
  Txt.

• Search, Next and Previous
  Txt.

• New Step
  Txt.

• Replace
  Txt.

• Move Up or Down
  Txt.

• Toggle Breakpoint
  Txt.

• Initialize
  Txt.

• Aspect
  Txt.

• Properties
  Txt.

Pin Specific Options (Context Menu)

Pin Specific Options

When a pin is selected in the editor:

• Open Editor
  Txt.

• Goto
  Txt.

• Search, Next and Previous
  Txt.

• Transfer
  Txt.

• Initialize
  Txt.

Settings

Aspect and behavour of a table driven block can be affected via the Settings Dialog.

---

Copyright © 2014-2024 eXept Software AG