Continue On Error Loadrunner
Contents |
if an error is encounter I am running a test with 18 scripts in it. Virtual users iterate error handling in vugen script every 5 minutes +/-60 seconds for an hour. However, once a
26377 Error Loadrunner
Vuser encounters an error, they move to failed status instead of ending the current iteration and firing again 404 error in loadrunner in 20 or so minutes. What is it I have neglected to do? Did I just leave a checkbox unchecked somewhere People who like this Close Like ·
Ssl Error In Loadrunner
0 · Add comment Comment 10 |600 characters needed characters left characters exceeded ▼ Viewable by all users Viewable by moderators Viewable by moderators and the original poster Viewable by all users 1 Reply · Add your reply Sort: Best Answer Answer by DavidMofOSI · Oct 27, 2014 at 05:10 PM Option 1: Try checking the " continue ssl protocol error in loadrunner on error" in the "design test's " runtime setting(RTS) --> Miscellaneous error handling options Open the test design Select RTS Miscellaneous Check the "continue on error" checkbox Press "OK" Press "Save" Then re -Run the test With the "continue on error " un -checked if the Vusers get an error , any error, he fails and quits the test run. If "continue on error" is checked the Vusers continue trying to do the next step in the iteration and then the next iteration. Option 2: You can add coding in the script to tell the Vusers when and if he get an error to end the iteration and start the next see the VuGen help "Function reference " for details on the LR command "lr_exit" Use these "Continuation Options" for the "Lr_exit" function, to tell the Vusers how to exit lr_exit(LR_EXIT_ACTION_AND_CONTINUE, LR_AUTO); Exit without any condition, and go directly to end action lr_exit(LR_EXIT_MAIN_ITERATION_AND_CONTINUE, LR_AUTO);Stop current action, and go to the next action lr_exit(LR_EXIT_ITERATION_AND_CONTINUE, LR_AUTO); Stop current iteration, and go to the nex
from GoogleSign inHidden fieldsSearch for groups or messages
ALM HP UFT & HP QTP HP LoadRunner HP Service Virtualization HP Agile Manager Our Work Blog White Papers About Us Company Overview The Difference https://northwaysolutions.com/blog/vugen-gracefully-handle-various-http-return-codes/ Alliances & Certifications Jobs Loadtester Incorporated Contact Us Home > Our Work > Blog > Vugen: Gracefully Handle Various HTTP Return Codes Vugen: Gracefully Handle Various HTTP Return Codes July 2nd, 2012 | Scott Moore There may be times where you want to build in logic for how your Vuser reacts to the various types of HTTP status error in return codes received throughout a script. For example, as web servers get overloaded, they may start sending 503 return codes. If you wanted to try and resubmit and finish out the transaction, this might be a more graceful way to handle the occasional 503 than just giving up and killing the iteration immediately. Of course, as the load error in loadrunner continues to increase, the 503′s will become more frequent and eventually you will need to give up. Giving it a few additional tries might better reflect users who are trying to resubmit their page rather than immediately abandoning the site. The code below is one way to loop a request up to 5 times and handle various HTTP return codes differently depending on what status code is being received. Action() { // Declare integers int HTTP_rc, retry_count; /* * This section includes the page request statement. * It switches on the * "continue on error" functionality just for this step. */ for (retry_count = 0; retry_count < 5; retry_count++) { lr_start_transaction("Transaction_Name"); lr_continue_on_error(1); web_url("Index.htm", "URL=http://webpage.server.co.uk/cgi-bin/gen001_serverselect.dll", "Resource=0", "RecContentType=text/html", "Referer=", "Snapshot=t1.inf", "Mode=HTML", LAST); lr_continue_on_error(0); // Capture the HTTP return code and store it HTTP_rc = web_get_int_property(HTTP_INFO_RETURN_CODE); // Condition statement: If less than 400, // end the transaction and carry on with rest of script if (HTTP_rc < 400) { lr_end_transaction("Transaction_Name", LR_PASS); lr_log_message("Index page displayed after %i att