• Jmeter as performance testing tool:
    Jmeter is one of the open source tools available in market for performance testing used by qa services.
    Performance testing is a practice which is performed to make sure that an application will remain stable and accessible under a particular amount of workload.
    Jmeter is used to analyse the performance of various services of any web application.
    There are numerous components of Jmeter which play a crucial role in its functionality. Thread group and Samplers are one of them.

    What is Thread Group:
    It is start point of test plan. It stores the configuration required for script execution.
    Thread group consists of below combination of three components:
    Thread Count, Ramp up time and Loop count.

    Thread Count: It specifies the largest number of concurrent requests/users that a server can handle.

    Ramp-up Time: The amount of time that any performance-testing tool takes to send all the threads for the execution. It is defined in seconds (time)
    Say that thread count is 10 and ramp up time is 100 seconds, then tool will take 100 seconds to get all threads up and run for execution.
    If first thread sent at 0th Seconds then moving forward, each thread will be starting after 10th seconds.
    Ramp up time should be sufficient so that unnecessary and large workload can be avoided from start of execution.

    Loop Count: It specifics the number of times to execute the performance test. It can be set manually or can be choose to execute forever in loop.
    Below is the example to understand the components of 'Thread Group':
    Thread Count = 20
    Ramp up Time = 100 sec.
    Loop Count = 4
    It means, every 5 seconds, 4 threads will hit the server.
    Once first threads complete the first round of execution, then second loop will start by executing same HTTP request.
    The execution circle will last until all the 20 threads execute all HTTP request four times.

    What is Sampler:
    Jmeter has two types of Controller: One is Sampler and another one is Logic Controller. Both are separate entities.
    Sampler is a requests itself. Sampler is the one which is dealing with sending out some discrete requests to server under the test.
    One Sampler may generate one or multiple results. These results can be viewed in various listeners (which provide the visual explosion to data about sampler component in form of text, graphs)
    Sample result also posses some attributes in it about success, fail, elapsed time, data size etc.
    For Example: A HTTP request can be added as Sampler in Thread group, if we need to perform some actions (GET, POST, DELETE) on HTTP Service.
    Below are some functional samplers:

    1. FTP request.
    2. HTTP request.
    3. SMTP request.
    4. BSF Sampler.
    5. JDBC request
    6. Java request.
    7. SOAP request.

    Top Software QA Services & Analysis
    Optimize your products for the global stage with QASource's comprehensive QA Services and analysis. Onboard a team of dedicated quality assurance eng…
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.