Skip to main content

Controller and its use in Loadrunner Software You Must Know

You can control and create the various scenarios of Loadrunner with the help of Controller—a powerful LoadRunner's tool. The events occurring in the course of each testing session is referred to as a scenario. Scenarios are effective in controlling the number of users and their various actions along with the machines that act as platforms for running their emulations. They are used to create load tests sessions that are required for checking the strength and reliability of your servers.

Given below is a list of primary items that need to be defined in your scenarios:
  1. Type of scenario-manual or goal oriented.
  2. Tests to run- the Loadrunner unit tests or scripts required to run.
  3. The machines upon which these tests will be run. 
  4. The number of Vusers (virtual users) required to run on every machine.
  5. Scheduling-which is linked to the ways of loading the Vusers.
  6. Measurements that require monitoring during the test runs. 
When the Controller is opened for the first time, it will prompt you to put in your selection for the type of scenario-manual or goal-oriented.

Goal oriented scenario:

In this type of scenario, you need to define the goals that you desire your test to achieve. After receiving your inputs, LoadRunner automatically constructs a scenario as per the goals set by you. Citing examples, you can set a goal for a particular number of Vusers to use the scenario simultaneously or define a different goal to set the various attributes of your server performance such as Hits per Second, Pages per Minute and/or Transactions per Second.

Manual scenario:

Here you can select unit tests/scripts and add Vusers in a manual way. You can also use your discretion to distribute them on all available machines.

Controller Technology:

While using the Controller, you can define a specific number of Vusers (apart from GUI Vusers) to create load on a particular server—by submitting their inputs directly onto the server. It is important to understand that Vusers don’t operate client applications and they access the servers by using the API functions of Loadrunner. The API functions are equipped to emulate inputs from actual applications. This takes place because Vusers do not rely on client software. As a result you can use Vusers for testing server performance—much before the development of the client software.

As Vusers do not enjoy a user interface, the volume of system resources allocated and required is minimal. This in turn permits you to run a higher number of Vusers on a specific workstation. The example given below illustrates the role of Vusers in a given scenario.

Suppose your web presence boasts of a database server that is responsible for maintaining information linked with your customers. This information will be obviously accessed by multiple customer service personnel located across the country. The web based server receives all queries, processes them in the right way and returns the responses across the internet to the requisite field personnel. You would like to test the response time of the full system, when many personnel access the server simultaneously. LoadRunner allows you to create a scenario using hundreds of Vusers—with each one accessing your server database at the same time. These Vusers allow you to measure and emulate the performance of Web servers and your database under the load of multiple users.

To emulate Vusers, you need to create a script that defines their actions. A Vuser script contains functions that controls script execution and specifies the various inputs submitted by the Vuser to the server. 

You can develop a Vuser script for the example stated above. The created script performs the under mentioned actions:
  1. It logs on to the Web application
  2. Connects directly to the database server
  3. Submits SQL queries
  4. Processes and retrieves the server’s response
  5. Disconnects the application from the web and server.

Comments

Popular posts from this blog

NeoLoad Interview Questions and Answers

Here are some of the interview questions and answers on NeoLoad:
What is NeoLoad?
NeoLoad is a performance testing tool designed to test different types of web, standalone and mobile applications.
What is the difference between Loadrunner, JMeter and NeoLoad?
Click here for differences
What are the different counters you monitor in NeoLoad?
Average Response Time(requests), average response time(pages), average requests/s, average throughput, current response time(requests), current response time(pages), current requests, current throughput, current users count, controller cpu load, controller memory load etc.
What are the different type of tools you can integrate with NeoLoad?
App Dynamics, CA APM Integration, Dyna trace integration, HP ALM or Quality Center Integration, Java and Jamo Solutions M-eux Test Integration, Jenkins Integration, perfecto mobile integration, selenium integration.
What are the different type of Operating systems you can monitor?
Linux Monitor, Solaris Monitor, AIX …

Sitescope Monitoring Tool Features and Monitors

Why Sitescope is called Agentless Monitoring Tool?
HP SiteScope monitors the application/infrastructure/server/operating system without installing any agent software on the system to be monitored. This feature makes the installation, usage and maintenance of Sitescope simpler when compared with the any performance monitoring tools like Diagnostics.
Sitescope Monitors:
Sitescope has also upgraded and changed drastically to meet the rapidly changing technologies and environments like virtualization and cloud computing. Using Sitescope we can monitor different web servers, application servers and database servers. We can also monitor operating systems Windows, Linux, Sun Solaris, IBM AIX. It has more than 100 monitors including Weblogic, Websphere, SAP, SIEBEL, SNMP, LDAP, Network Monitor etc. HP SiteScope can also monitor cpu utilization, response time, disk space, and resource availability of a variety of host types and application platforms.
Sitescope Features:
SiteScope provides failover …

LR Functions with Examples | Loadrunner Functions with Examples

LR Functions in Loadrunner with Examples.

lr_abort Stops the script execution.lr_advance_param It will take the next value in the parameter list.lr_continue_on_error Continue on error even if the request is failed.lr_convert_string_encoding Converts a string to a UTF 8 or Unicode.lr_db_dataset_action Validates database contents by setting checkpoints.lr_db_connect Connects to a database.lr_db_dataset_action Performs an action on a dataset.lr_db_disconnect Disconnects from a database.lr_db_executeSQLStatement Submits an SQL statement to a database.lr_checkpoint Validates the value of a parameter against an expected value (checkpoint).lr_db_getValue Retrieves a value from a dataset.lr_debug_message Sends a debug message to the LoadRunner output or Application Management agent log file.lr_decrypt Decrypts an encoded string.lr_disable_ip_spoofing Disables IP Spoofing.lr_enable_ip_spoofing Enables IP Spoofing.lr_end_sub_transaction Marks the end of a sub-transaction.lr_end_transaction Mark…