A while ago I answered the following question on SearchSoftwareQuality.com’s Ask The Software Quality Expert: Questions & Answers .

I am a beginner software tester. I want to learn HP's Quick Test Professional (QTP) better and make my own test scripts, but I'm unable to find good material to teach me from scratch. Can you please help?

Here is a clip from my answer:

Learn about QTP

Finally, the last thing you'll want to learn is the tool you're using. It's important that you understand the tools you're using, but not nearly as important as knowing when to apply it or under what conditions. Everything else in this response leads up to this. If you know how to test and how to write good code, and you know the historical issues in test automation, then you're ready to dig into the tool. It provides a context for really understanding what the features do, what they don't, and how to apply them. To that end, here are some resources for getting started in HP Mercury Quick Test Professional.

First, read the manual. I know that sounds silly, and there aren't really manuals any longer (just online help), but still -- read it. It's dry, boring and information-packed! You wont remember everything you read, not even half, but you'll get exposure to everything. And you don't really have to read it all -- skim liberally. You need to know this stuff.

Next, I recommend setting up some RSS feeds. Content every couple of days is a good pace for learning tips and tricks. And if you have time, you can always go back and look at existing posts. I recommend the following sites:

• http://www.learnqtp.com/


• http://qtp.blogspot.com/


• http://quicktestprofessional.wordpress.com/


• http://quicktesthp.blogspot.com/

They aren't the best-formatted blogs, and a few may have a lot of ads, but they have good content.

You can find the full posting here .

A while ago I answered the following question on SearchSoftwareQuality.com’s Ask The Software Quality Expert: Questions & Answers.

What is the likelihood of capturing accurate load testing results in a virtual test environment? We use LoadRunner/PerformanceCenter for performance testing. Our company is in the process of making use of virtualization. It seems this may be ideal for functional test environments, but not for performance test environment. What is your opinion?

Here is a clip from my answer:

Some research on the topic has found that virtual environments don't scale as well as non-virtual environments. In a study by BlueLock, a company that provides IT infrastructure as a service, they found that "the number of simultaneous users that could be handled by the virtualized server was 14% lower than the number of simultaneous users being handled by the traditional server configuration."

This is consistent with my experience testing financial service applications in virtual environments. Scott Barber, fellow SearchSoftwareQuality.com expert, recently gave a talk on the topic. You can find the PowerPoint slides for the talk here . In those slides he points out some other common challenges with working in a virtual environment.

If you don't have much choice, or if you have a lot of pressure to make it work, I would recommend that you perform a comparison performance test to prove out the new platform. If you can do that successfully, you'll have some confidence that the platform is comparable. But just be aware that over time, as the application changes and the server configurations change (both virtual and the physical servers in production) your comparison will become outdated. It may happen faster than you might think.

As Scott points out in his talk, the problem isn't necessarily virtualization. It's that we don't always pay attention to all the other factors that affect performance. Differences in software and hardware configurations, network devices, geographic location, firewalls and other security measures, and a host of other factors all affect performance. Virtual environments often only make it more complex to track everything since they introduce their own overhead, rely on different network devices, and can reside in different physical locations.

You can find the full posting here.