When a verification point failure occurs in RPT (Rational Performance Tester) scripts, the default behavior is to report the error and then continue to the next page element (transaction). Starting in RPT 8.2, you can select the way you want your RPT scripts to handle verification point errors. Normally, you want the script to exit, but other options are available that may be more appropriate in some scenarios.
This blog explains how to set these page element exit policies in your RPT script.
Users who are playing back RPT scripts under the Robotic Response Time agent in ITCAM for Transactions V7.4 will find this presentation especially useful.
1) Display your script in RPT test mode. Right-click the parent node and select Verification Points > Enable Page Title VPs from the pop-up menus.
3) RPT acknowledges that it has added the verification points. Click OK.
5) In this example, the default action is to continue if the verification point is detected. When you use this default for each page element, each page element generates a verification point failure if the web page is not accessible – for example, if the application or the application server is offline. To change the default behavior, click Change.
6) Note the different options available for continuing or ending script execution. If you select Exit Test, you see one verification point failure in the scenario where the web page or the application server is down. In most cases, this is the best selection, because you don’t want to flood Omnibus or the Robotic Script Verification Point Failures workspace with failures.
9) Run a test in RPT to compile the script. If no errors are reported in the RPT test log, export the script to the AMC (Application Management Console).