Replies

  • There are a lot of elemets which can be debugged starting from post-processors and ending with whole JMeter Engine connection having JMeter sources. The easiest and the most frequently used is View Results Tree listener which provides comprehensive information on request/response details and has a number of built-in tools to i.e. debug regular expressions, xpath queries, etc. See How to debug your Apache JMeter script guide for more details on each debugging technique mentioned.  

  • Thks buddy :) it is helpfull.

  • Nice 

  • Use Debug Sampler : http://jmeter.apache.org/usermanual/component_reference.html#Debug_...

    Useful ways to debug JMeter as far as I know:

    • insert a “Debug Sampler”

    Debug Sampler Screenshot

    the “Debug Sampler” will emit “everything that’s known” to JMeter. That output can be displayed in the “View Results Tree Listener”:

    Debug Sampler Result Screenshot

    • have a look at the JMeter log file (which is usually dumped from where you’ve started JMeter)

    • check the output of one of the listeners such as the “View Results Tree Listener”.

    • if you need to debug regexes of a “Regular Expression Extractor” then you can have a look at the source code of the page you want to extract a value from inside the “View Results Tree Llistener” and enter the same regular expression in the “Search” field (searching is only implemented in JMeter > v2.4).

    Debugging Regexes Screenshot

    In that picture you can see JMeter matching and displaying the regex entered in the search field inside an HTML page retrieved though the “HTTP Client Sampler”.

    Apache JMeter - User's Manual: Component Reference
This reply was deleted.
    results->result as $result) { ?>
  1. jobtitle;?>
    company;?>(formattedRelativeTime;?>)city;?>, state;?>
    Welcome to Mobile QA Zone, a Next Generation Software Testing Community.Invite your friends to join this community.Write to us to become a featured member.