Trace analysis¶

This category contains test steps regarding trace analysis. Using these test steps one may create an analysis job explicitly and adopt trace step results into the test case report.

Enqueue analysis job ¶

By default analysis jobs are created automatically. Further information regarding this topic can be found in the section describing the creation of analysis jobs. In comparison to this automatic mechanism the test step Enqueue analysis job allows for more control and enables to realize conditional trace analyses.

This test step creates an analysis job explicitly and passes it to the waiting queue that stores the analysis jobs prior to their execution. The usage of this test step in a certain package prevents analysis jobs from being created and enqueued automatically within the aforementioned package. Calls to subpackages are not affected in this way as long as the test step is not used there. Regardless of the way an analysis job is created, it is always executed after the test case.

In the configuration dialog of the test step one can select a (local) trace analysis within the considered package for the analysis job creation. The test step does not support trace analyses located in other packages. However, the local trace analysis may include references to other trace analyses. In the generated report performing a doubleclick on the test step or using the context menu (Go to) one can easily navigate to the configured trace analysis.

If the test step is used in a package that contains trace analyses which are not associated with any analysis job, an error will be displayed in the messages window during package execution.

There are several ways to specify the recording of the analysis job. Besides using the test steps of the category Trace recording one may explicitly provide a recording in the tab Signal recordings of the package editor.

Interaction with other test steps:

• The test step can be used before or after the “Add Trace” test step. The order of these test steps is only important, if there are more “Add Trace” calls than “Enqueue analysis job” test steps: More precisely, in the scenario in which the test step is used after several “Add Trace” calls the recording of the last “Add Trace” test step is used for the analysis job. The recordings added by the surplus “Add Trace” test steps are neglected.

• Likewise the test step can be inserted into the test case between the test steps “Start Trace” and “Stop Trace” or after the “Stop Trace” test step. The analysis job is then based on the running or most recently finished recording, respectively.

• The test step may be used within test steps of flow control like for instance If-Then-Else or Switch-Case. Such constructions can be considered as conditional trace analysis: The analysis job is only created and passed to the waiting queue if the corresponding condition of the test case test step is met.

At the time of the analysis job creation a snapshot of the package variables is taken and passed to the analysis job, i.e. in the analysis job variables have the last recent value before the time of the analysis job creation.

If the option carry over result of analysis is activated then the “Enqueue analysis job” test step will be given the overall verdict of the analysis job in the test case report.

Incorporate trace step result ¶

Using the test step Incorporate trace step result one can take over the report result of an arbitrary trace step into the test case report.

In the configuration dialog of the test step one can select the trace step of a local trace analysis whose result shall be transferred to the test case report. In the generated report performing a doubleclick on the test step or using the context menu (Go to) one can easily navigate to the configured trace step.

Request analysis ¶

The test step Request analysis is intended for use in stimulation packages and allows the coupling and conditional execution of an analysis package at project level by “implementing” the requested analysis. The step is evaluated with ERROR if no analysis package implements the requested analysis. Optionally, the result of the executed analysis can be taken over into the test step result.

In the generated report performing a doubleclick on the test step or using the context menu (Go to) one can easily navigate to the performed trace analyses.

More information about the use case and usage can be found in chapter Stimulation package and analysis package.