Dialog: Test Progress Symbol: Function : The dialog provides information about the test script processing which is currently running. It also contains buttons and views for debugging the test script.

Element: Test Script Function : The element manages the metadata of the corresponding test script. The element is always located at the top position in the test script. Call : Test Script element in t

Command: Find All References Function : The command searches for test scripts which call the selected test script and shows the search results in the <test script name> (<version>) – Referenced by dia

Command: Install Test Script Function : The command imports and installs one or more previously exported test scripts and saves them in the test repository. Then the Open dialog opens for selecting th

Pragmas in Test POUs The following pragmas identify a program or function block as a test POU and define test case properties. Table 75 . Simple test Pragma Optional Description {attribute 'test'} Ide

Implementing a multitest POU To implement many related test cases on only one test POU, you can use the pragma {attribute 'test' := 'multitest'} , which decorate a test POU with ETrigA behavior with t

Creating a Model-Based Test with a Test Table The aim of a unit test is usually to determine the correct operation of a function block or program. You can formally implement the required test code as

Implementing a single test POU Creating a framework for the test case A test case is a function block which follows a specific scheme. To make it easier to follow the scheme, we recommend using the wi

Command: Save Test Report Function : The command saves a test report in the test database in the folder which has the same name as the folder of the test script. The test report is also saved in the f

Editor: Test scripts Function : The test script editor provides the implementation of the test run. The top node is always the Test scripts test element. At least one Test case test element is below t