In early December, I was travelling down to the HPE Discover conference in London. I think that I’d allowed myself to be slightly less organised than normal, because rather than some far flung destination, I was heading to London on the train. This lack of prior planning and preparation caught me out when I realised that I’d managed to leave my laptop power supply at home.I was travelling on Saturday afternoon and realised that I faced two days of meetings before the conference started without my laptop.
In order to adequately assess what’s happening to the underlying Infrastructure/Hardware during a performance test, monitoring is essential. Here at Trust IV, we decided to integrate HP’s SiteScope product into HP’s new cloud performance testing offering, StormRunner Load.This is how I setup the Infrastructure.1. Following the steps below, I created a SiteScope Server in our Internal Demo Network, behind the Trust IV firewall.
****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 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.