KabInfo.Net                                     

Q:Upgrade of Test Director from 7.x to 8.0; Discuss best approaches and complications and pitfalls and benefits from the upgrade also things to watch out for...

A:We have a "Best Practices" document in the KB about upgrading to TD 8.0. CSO website - Download section or KB, you can search for "Best Practices"


Q:We are using Loadrunner 7.8 FP1.In that we have load distribution graph, response time Vs transactions per sec (rounded to nearest sec). We are running tests on j2ee application where expected response times are in milli seconds (ex 150 millisecond per method). Because rounding to sec we are seeing all transactions below 1 sec. Is it possible to change response time scale as we needed in to milli seconds? We would like to see response time distribution respective to transactions per sec for whole scenario. Which is going to show us if there any spikes in response times.

A:Today, the Analysis UI reports in seconds, even though the raw data is available in milliseconds. We have taken both of these as enhancement requests for future releases.
Q:I am running an endurance test on the client using QTP. The test is set to run 500 times. Is there a way to set a counter on the number of times the script actually ran when it quits before the 500?
A:DataTable.GetCurrentRow holds the current iteration. When QTP quits, it can write this value to the report.
You can use environment variables or a regular variable to keep track of the number of times to run the script. You can then write this value to the runtime data table. When the script quits, go to the runtime data table and look at the value. If the script is based on iterations, then you can use the built-in environment variable "ActionIteration" or "TestIteration" which will give you the current iterations for either the test or the specific action.
Q:What are the differences between QTP 8.0 and Quality Center 8.0 vs. QTP 8.2 and Quality Center 8.2?
A:We have created a product alert that describes what's new in Quality Center and QTP 8.2. You can find the alert on the CSO website. In addition, Mercury will host a customer webinar on December 13th on Quality Center 8.2. Please see the CSO website for registration. We will also make the recording of the webinar available on the CSO website for subsequent viewing.
Q:How are checkpoint baseline values and the purpose of the checkpoint communicated back to the BA in BPT ?
A:The idea is to provide these as custom keywords. The QTP engineer should create "verification" keywords (functions) and the BA will use them in QA while defining the component steps. These functions can be defined either using the standard checkpoint mechanism QTP provides, or any other mechanism the QTP experts builds.

A checkpoint contains a number of properties / values and we use these properties / values to do the comparison at runtime. We then write the status of the checkpoint back to the QTP Report. If the report is stored in QC then it's written to QC; if the report is stored on the file system then it's written to the file system.