****UPDATED****See Floris Kraak's comments below, he has a much more elegant solution.......****UPDATED****It is common practice for testers to use local HOSTS files to direct traffic from Load Generators to the application under test. If possible the URLs should be parameterised, this allows the URLs to be changed quickly, for example when switching between development and test environments. Some web servers, however, host multiple websites and direct traffic to the appropriate site using host headers.
This is the third article in a series describing script improvements that I recommended to a client during a recent engagement where I was advising on a LoadRunner to Performance Center migration.
This is a follow-up to a blog article that I wrote after a recent engagement at a client site where I was involved in planning a migration of performance tests from LoadRunner to Performance Center. The original article had some tips about the use of test data. This article expands on that.During my time on site, I spent some time reviewing my client's scripts.
During the installation of LoadRunner, if you select "Allow virtual users to run on this machine without user login", the LoadRunner agent will run as a Windows system service called "LoadRunner Agent Service". If you choose "Manually log in to the Load Generator ", the LoadRunner agent will be run as a process named magentproc.exe.
