Assertion¶

An assertion validates a contained trace step. It can hold exactly one trace step, which must be enabled. Otherwise an error is being raised. An assertion is given the verdict SUCCESS, if and only if all parametrized expectations are met. Otherwise a valid assertion is rated FAILED. If an assertion manipulates the propagated result, this is indicated in the report by means of a revaluation. The number of unfulfilled expectations is reported as result text of the assertion. A more insightful analysis of the configured expectations is provided in the details of the assertion in the analysis report. If there are no expectations at all, the verdict of the assertion will be the same as the verdict of the contained trace step. An assertion can not have any of the elements block, IfDef or SwitchDef-Case as direct child trace step. If the assertion validates a trace step contained in a trigger block, all expectations are matched against each trigger range.

For nested assertions, it is checked for outer assertions whether all expectations of inner sub assertions are being met. Otherwise the outer assertions are rated FAILED, too.

Expectations

If the Evaluation of the contained trace step is subject to an expectation, then the assertion can only be rated with SUCCESS, if this expectation (‘NONE’, ‘SUCCESS’, ‘INCONCLUSIVE’, ‘FAILED’ or ‘ERROR’) is matched by the actual result of the trace step. The expected result may also be parametrized by a list of results like [‘SUCCESS’, ‘FAILED’] or by means of a package variable.

If the contained trace step is expected to return ‘ERROR’, one may additionally check the error message of the trace step, e.g. ‘Error: #54’. Here, the special characters ‘*’ and ‘?’ are interpreted as wildcards.

The usage of wildcards is also supported in the subjacent input field in order to check the result text of the trace step.

Execution time (episodes only)

If the contained trace step is an episode, then one may assess that the actual execution time stays within parametrized lower and upper bounds Min and Max, respectively.

Irrespective hereof, one may formulate expectations on the verdict or the error message of the contained episode.

Description

The name of the assertion is generated using the configured expected verdict of the contained trace step. An optionally provided Description is shown in the respective column.