| || |
How to handle correlations that do not always occu
Before I start I want to thanks everyone on this site for all their help and advice!
Okay, now to the meat:
As stated in previous questions i am working on an application that uses a shopping cart to process orders, if an order is successful it gives an order number.
There are also a number of conditions that I need to trigger as part of an effective performance test where an error screen is presented instead of the order number due to different SQL calls made by each sub-process.
I have a series of text checks to determine what screen is returned and further logic branches from there.
The issue I am having is that if an order number is returned, then I need to use that later in processing, thus I have to make a correlation call before the page is retrieved or I do not get the order number (if present).
However, if there is no order number on the screen (i.e. - the correlation fails), then an error is sent to the controller during the run, which throws off my statistics.
Is there a way to either 1) stop the reporting on the unfound correlation as an error or 2) somehow trap the order number after the logic has determined which screen was retrieved?
Re: How to handle correlations that do not always occu
Re: How to handle correlations that do not always