Miscellaneous¶

This category summarizes the test steps which do not fit in with any of the other categories.

Assertion¶

This test step provides the possibility to assess the result (SUCCESS, FAILED, ERROR, …), ERROR message (e.g. “*Error: #54*”), execution time and entries in log files of exactly one subsidiary test step. The expectation field of the Assertion in the test case editor contains the expectations defined in the test step. The expected test step result may also be parameterized by a list of results like e.g. [‘SUCCESS’, ‘FAILED’] or by means of a package variable. The name of the Assertion contains the expected verdict. Additionally, an expectation for the ERROR message can be defined. When all expectations are satisfied, the Assertion verdict is SUCCESS. The verdict is shown as post evaluation. If any of the expectations are unsatisfied, the Assertion verdict is FAILED. The count of unsatisfied expectations is shown in the value field in the test report. A more precisely analysis is shown in the detail view of the test report item. If there are no expectations, the verdict of the Assertion will be the same as the verdict of the contained test step.

Log file entry¶

This test step writes a string (or a list of strings) into a log file. In that way, one can comfortably fill a self-selected file with results while the test is running. The file can be identified by an absolute or relative path, just the ending is fixed as .log. If the test step is entered into the test run several times, one and the same file may be used (new entries are added). It is also possible, by indicating other files, to write in several files.

In order to add your own outputs to the ecu.test test report, please use the test step Report.

Report¶

This test step allows you to add your own information to the ecu.test test report. The dialog is divided into several sections:

Column texts: These entries represent the corresponding values in the columns of the test report.

Attachment: Here you can provide a file or a folder. Paths can be relative to the workspace. It is also possible to enter the file origin as a hyperlink. The path will be documented in the report in the test step. It will also be listed in the package report’s summary page in the tab ‘Artifacts’. Optionally, the file can be copied into the report directory during test execution, if it exists on the file system.

Report comment: If the report comment is activated, then there will be the mark of a comment in the report row of this test step and the content can be seen in the details. This comment can be read automatically via the Report API, e.g. for tags that can be interpreted by test.guide.

Note

If the test report is to be exported to test.guide, the rules for report comments specified there must be followed; otherwise, the upload will fail!

Table: The table will be added into the test report under the details of this test step. The values in the first row will be formatted as header of the corresponding column. If the table shall not be filled in a static manner, the control box Variable can be activated. Now you can enter the name of a ecu.test variable whose contents will then be inserted into the test report. In order to have a multi-line or table display, the variable must be of the type Matrix.