Skip to main content

    Editor: Reports

    Function: The test report contains the detailed results of a test run.

    Call: Test report in the Test Manager view, on the Reports tab

    Tip

    When the test run is started, you can specify whether the report should be "verbose" (default) or reduced. The reduced version saves memory, but it does not include any information about the values for variable assignments. You can also set this from the command line: --no-var-recording argument for the --executecommand command.

    Table 78. Overview

    Link Summary

    Jumps to the respective location in the report

    Link Details

    Date

    Date and time of the test run

    Example: 03/01/2018 09:00

    Script

    Script path with version

    Example: Example.CounterTest (4.2.3.0)

    Tester

    Tester name

    Example: t.tester

    Test settings

    Possible values:

    • Verbose: The Create verbose report option was selected in the Execute Test dialog (after clicking the Execute Script command).

    • None: Settings not enabled.



    Table 79. Summary

    Bar

    • Green: Test cases which have ended successfully

      When the test is successful, all test cases and the entire bar are displayed in green.

    • Red: Failed test cases

      The test run is completed with partial success. The bar is displayed green and red according to the distribution from successful to failed.

    • Gray: Skipped test cases

      A test case is skipped when it has not been executed due to the execution condition of the Choose test element.

    Statistics of the test run

    • Total test cases

    • Succeeded

    • Failed

    • Skipped

    • Execution time



    Version information

    Information, for example about the development system and/or of the runtime system

    Requirement: The test script contains test actions of the TestManager.Testreport test driver.

    Example: AddVersionInformation(TestManager.Testreport)

    Table 80. Details

    Result tree

    Lists the results of the test run in a tree structure

    For each test element which is run, a branch is displayed containing the name of the test element and its details. These are mostly actions, but they can also be test cases, calls, assignments, or another test element.

    Note: By selecting the Create verbose report option in the Execute Test dialog, you can include the following information in the report: assignments and calls with values of variables and parameters, conditional operands for choose elements. Do not select this option if you want to reduce the scope of the report and the required storage space. You can view the current setting at the top of the report in the Test settings.

    • Test Case, Test Action: <name> – <result>

      • Succeeded: Displayed in green

      • Failed: Displayed in red

        Including a detailed description with an error message

    • Choose: <name> – <result>

      Entry for each branch in the order of the flow

      Branches which were not executed contain only the top element and they are not expanded. These kinds of branches get Skipped as the result.

    • Test element Call: <name> – <result>

    [+]

    Expands the element and shows the details of the test run

    [-]

    Collapses the element

    Button Collapse All

    Shows only the top node with the test script name

    Button Collapse succeeded

    Collapses the succeeded test cases

    Button Expand All

    Shows all test element results

    Button Show parameters

    Shows the parameters with passed values

    Parameters are included in the test report only when the Verbose test setting is enabled.

    Example: BasePath -> C\ProgramData\CODESYS Test Manager

    Button Hide parameters

    Hides the parameter information



    Save as HTML

    Opens the default Windows dialog Browse for Folder to select a folder

    Then the test report is saved there as an HTML file.