Button bar packages

Horizontal button bar

All buttons contain tooltips for details. If a button function is unclear, moving the mouse over it opens a help text after a short time.

../../../_images/Buttonleiste.png

Buttons:

  • Test execution:

    • Execute test case and trace analysis

    • Execute test case and trace analysis interactively

    • Debug test case and trace analysis

  • Checks and language

    • Check package

    • Test case language

  • File operations:

    • New

    • Open

    • Save package

    • Save package as… / as template

  • View:

    • Expand all test steps

    • Retract all test steps

  • Edit test steps:

    • Cut

    • Copy

    • Paste

    • Undo

    • Redo

The functions Check package and Check package translation will be afterwards explained in more detail.

Vertical button bar

Frequently used test steps are arranged on the left side of the package editor. This button bar can be configured by the user. The button with the wrenchicon leads you to the configuration dialog.

../../../_images/Buttonleiste_Utilities.png

  • Frequently used test steps:

    • Block

    • Calculation

    • Wait

    • Loop

    • If-then-else

    • Multi-Check

    • Comment

Check package

../../../_images/Packageeditor_Test.png

Before running a package it is useful to check if problems may arise during execution. There may be, for example, faulty package references or missing mapping references. Call up the check module of ecu.test by means of the button Check package in the button bar. Now ecu.test will check all test steps, including referenced packages. By default ecu.test will check for the following:

  • Faulty package references

  • Missing mapping references

  • Undefined variables

../../../_images/Package_Pruefen.png

By means of the button Create missing mapping items in global mapping space all faulty mapping references are added to global mapping, so that the necessary adaptations can be made quickly across all subpackages. This is a fast and comfortable function for adapting a package to the specific conditions of a test site, especially if the package is to be carried out elsewhere.

If a problem is double-clicked, ecu.test opens the corresponding package in the background and highlights the test step concerned (it may be necessary to scroll manually to the respective point in the package). When all the desired packages are opened, the check dialog is closed by OK, and the problems can be treated.

Info

We speak here only about possible problems. ecu.test cannot realize at this moment, for example, which test steps are not being run at all because of conditions.

Info

It is also possible to implement your own package checks. These custom checks create the possibility to also offer your own fixes in a context menu which can be applied directly in the same check dialog. For this purpose the supplied examples can be copied into the workspace when starting ecu.test. The interface to be used is described in <ecu.test-Installation directory>/res/CustomChecker/api. Custom package checks can be placed in the workspace below UserPyModules, so that they are recognized by ecu.test.

Select current test case language

../../../_images/Testfallsprache_Auswahldialog.png

The current test case language can be selected from the activated test case languages. The flag symbol on the toolbar icon indicates the currently set test case language. The test case language to be used can be changed in the menu. This setting takes effect immediately without a restart and affects the display of the following elements:

  • Name, Parameter and Expectation/Value of Block test steps

  • Comments of the test steps

  • Initial values of String variables

Deactivated languages are grayed out and cannot be selected. Languages can be activated and deactivated via the option Configure test case languages… or in the test editor workspace setting.

This current test case language, along with other test editor settings, is stored in the file testeditor.xml.

The language toolbar menu also features the option Check translations, which is described below.

Check package translation

../../../_images/Uebersetzung_Dialog.png

If a package has been drafted for multilingual application, this option serves to show all translatable texts for reviewing. Texts from languages not enabled for test cases, will not apear.

Review legend:

  • Fields marked in red highlight inconsistent translations. This is the case if the test case language of an item has been edited, without updating the corresponding translation.

  • Fields marked in green show the user that he has reviewed entries.

  • Fields with text in italics show suggested translations for non-translated passages.

By hitting Apply or OK the user approves all inconsistent and suggested translations.