LoadRunner – Runtime Settings – Content Check

LoadRunner - Runtime Settings - Content Check

LoadRunner is well-known for its simplicity which makes performance testers’ life easier. In the LoadRunner Scripting topic, we discussed the content check in detail. Even you got the information about the different type of content checks in LoadRunner i.e Text Check, and Image Check along with the content check functions which are:

  1. web_reg_find
  2. web_image_check
  3. web_global_verification

This article will brief you about the content check setting available under runtime settings of LoadRunner. Using this setting you can enable or disable the content check in the script and also create some global rules which are applicable to all the transactions present in the script.

LoadRunner - Runtime Settings - Content Check Tab
Figure 01: Content Check Setting

What are the settings available for Content Check in LoadRunner?

  1. Add Application: 
    This button will add an application in the tree pane with the default name like Application_1. Change the default name and provide a unique name which belongs to the application. It helps to identify the content check setting when you export it.
LoadRunner - Runtime Settings - Content Check - add application
Figure 02: Add Application
  1. Add Rule: 
    You can use this button to add the content check rule under an application. You can add multiple rules under one application.
LoadRunner - Runtime Settings - Content Check - Add rule
Figure 03: Add Rule
  1. Delete: 
    You can use this button to delete the application and rule. Select the application or rule (which you want to delete) and click the ‘Delete’ button
  2. Import: 
    You can use this button to import existing content check rules
  3. Export: 
    You can use this option to export the current rules. The rules can be exported in a .xml file. The content check rules can be easily exported and used in another script. This is a timer-saver option.
  4. Search:
    You can search the text either by specifying the exact text or boundary of the text.
    1. Search for text: Enter the text which you want to match in the response
    2. Search by prefix and suffix: Enter the prefix and suffix of the text which you want to match in the response
  5. Match Case: 
    To make the text search case sensitive
  6. Fail if: 
    The action needs to be taken by LoadRunner when the text found or not found.

How to add content check rule in LoadRunner?

  1. Go to Runtime Settings
  2. Select ‘Content Check’ under ‘Internet Protocol’ category
  3. Click ‘Add Application’
  4. Rename the application name (optional)
  5. Click ‘Add Rule’ by selecting the application
  6. Rename the rule (optional)
  7. Select either ‘Search for text’ or ‘Search by prefix and suffix’ as per your need
  8. Add the text or prefix/suffix in the respective text field(s)
  9. Check/uncheck the ‘Match Case’ condition as per your requirement
  10. Set ‘Fail if’ condition ‘Found’ or ‘Not Found’ as per your requirement
Figure 04: Content Check Rule

Note:

  1. You can delete, import and export the rules using ‘Delete‘, ‘Import‘ and ‘Export‘ button.
  2. Click ‘Use Defaults’ button to reset the setting.

Important Points:

  1. The use of web_reg_find functions is good, but when you get an error LoadRunner reports it as “failed to find text” instead of something more descriptive, so you can use Content Check rule.
  2. You can always create rules for any error messages you find during scripting and, if you receive an error while running a scenario, you will add the error message from the snapshot in the scenario results directory.

Leave a Reply

Your email address will not be published. Required fields are marked *