You can define resources used in your test to be non-critical, so that the test can replay successfully even when actions performed on these resources fail. For example, an image or a Java applet that failed to download may not be critical to your business process.
Prevent unnecessary failures due to errors with non-critical resources
- In the Runtime Settings Preferences view, the field List non-critical resource errors as warnings must be enabled (default value). See Preferences View - Internet Protocol.
- You classify a resource as non-critical, by defining the value of the Resource attribute in the function, as described below.
The classification of a resource as critical or non-critical depends on the value of the Resource attribute in the function, as described below.
If Resource is specified:
- Resource = 0: The resource is always critical.
- Resource = 1: The resource is always non-critical.
If Resource is not specified:
- If Method is not Get: The resource is always critical.
If Method is Get:
RecContentType is omitted RecContentType is text/html RecContentType is not text/html Critical Critical Not critical
The resource in the following function is non-critical because Resource is 1: