TestingWorld

          Configuring Vuser, Controller and Load Agent using MI Listener To Configure Vuser, Controller and Load Agent using MI Listener , make sure MI listener is running Running Vusers over a firewall : To set up your system to run Vusers over a firewall Ø   On each load generator machine that will be running over a firewall, configure the LoadRunner agent to communicate with the MI Listener. Ø   Configure the Controller machine to recognize the load generator and MI Listener machines. Configuring LoadRunner Agents over the Firewall Ø   Stop the LoadRunner agent by right-clicking its icon in the system tray and selecting Close. Ø   Run Agent Configuration from Start > Programs > LoadRunner > Advanced Settings, or run \launch_service\bin\AgentConfig.exe. Ø   Select the Enable Firewall Agent check box, and then click Settings. Ø   The Agent Configuration dialog box opens. Ø ...

In a regular LoadRunner load test scenario (not over a firewall), The Controller has direct access to the LoadRunner agents running on remote machines. This enables the Controller to connect directly to those machines. When running Vusers or monitoring applications over a firewall, this direct connection is blocked by the firewall. The connection cannot be established by the Controller, because it does not have permissions to open the firewall. LoadRunner solves this problem by using a communication configuration based on HTTPS or secured TCP/IP. This configuration uses the standard SSL port on the firewall (port 443). The MI Listener is a component that serves as router between the Controller and the LoadRunner agent. When the LoadRunner agent connects to the MI Listener, the MI Listener keeps a listing of the connection to the agent using a symbolic name that the agent passed to it. When the Controller connects to the MI Listener, it communicates to the MI Li...

                                       Performance Testing Goals As we are moving into various aspects of application which consists complex architecture. i have described earlier in my post ,  when and which type of applications can undergo performance testing. Why we do performance testing? what is goal of this type of testing?  we can choose to do performance testing on our application to achieve below mentioned goals: 1. Either to find that how our application's performance or does it meet performance criteria. 2. To Compare two systems to know which perform better 3. To measure which parts of the system or workload cause the system to perform in bad manner i.e. finding the culprit components of system which may impact performance of application. 4. To establish a performance benchmark or baseline for  performance of our application ·  ...

                      Virtual User Concept in Performance testing As i have defined "Concurrent user" in one of my post before, but this is one of the important concept which need a good grasp for a performance tester. Let me again re-phrase the user concepts in terms of performance testing: User can be termed as "Virtual User" in performance testing perspective since during the test run , users used are not the real users. Virtual users can categorized into various types in terms of understanding, but " Simultaneous Users " and " Concurrent Users " are widely used as concept in testing. What is Simultaneous Users? The users who have a valid session in the server. Each of the users would be performing different actions like one doing login , other viewing the reports, etc. What is Concurrent Users? The users who have a valid session in the server & they are performing the same operation at any poi...

                  Parameterization in Load runner A method to replace a static value with other values picked external data source like excel or DB or notepad is known as Parameterization . Usually, We use parameterization for those value which are user inputs or static value which can change basis of no of users Load runner also has this option. Load runner provides various types of parameter types to use this feature. There are various types of Parameters available in load runner: 1.                    File  2.                   Table  3.                    XML  4.      ...

How to Capture Thread Dump in JVM Let’s see how to capture thread dump of application in java. We can capture it with or without Console. Method to generate Thread dump with Console: 1. On Windows: ·          Press Ctrl-Break in the command console you used to start the IDE  If the console isn't opened (in case you started the IDE using the default desktop icon): launch the IDE using a console window  -Start Command Prompt -go to {netbeans-install-dir}/bin -type nb.exe configure the desktop shortcut to launch the nb.exe instead of netbeans.exe (default) NB7 and higher - just run netbeans.exe from console. If NB is started by shortcut use "--console new" option to open console (netbeans.exe --console new). ·          The thread dump is printed into the command console. 2. Console on Unix, Linux, Mac OS X ·    ...

Thread Dump is another good way to analyse about application behaviour. What is Thread dump? Thread dump is list of threads which are currently active in Virtual machine. Thread dump is very useful when it comes to know below things: 1.        How many threads are active 2.       Total no of threads used in one work flow 3.       Which thread is doing what in application In short we can also define thread dump as a snapshot of state of all threads in a process of application.