Testing is Rocket Science Not Brain Surgery

8 Comments so far ↓

• vinodmenda // Dec 19, 2009 at 12:31 am

  I am using LR 9.1 version and using HTTP/HTML protocol.
  when i’m executing 10 transactions in Controller, 7 transactions failed due to Stepdownload time out errors. I increased the timeout from 120sec to 999secs. But this time 4 transactions failed.
  Help me what should I do to resolve this issue?

  Vinod

• vinodmenda // Dec 19, 2009 at 12:39 am

  Hi,
  Can I have the description of how to Reporing bugs (template) in Loadrunner.

• vinodmenda // Dec 19, 2009 at 12:45 am

  Hi,

  1)How do you/on which basis will you estimate test duration(run length) in LoadRunner?

  2)How do you/on which basis will you estimating target load levels in loadrunner?

  3)How do you/on which basis will you measure the current VUsers in LoadRunner?

  4)Which document gives us information about Transaction Mix?How do we prepare Transaction Mix?

  Regards,
  Vinod

• Administrator // Dec 20, 2009 at 3:48 pm

  I would suggest any standard template for functional defects modified with categories around capacity and response times. You want to make sure you note the build number you tested and the type of test you performed, whether it was a baseline or a stress test or a volume test. Differentiate between errors that are related to a violation of SLA or defects around the capacity of the system. Note the lower-level technical details if they are known such as the method or subroutine that is performing poorly or any related SQL.

• Administrator // Dec 20, 2009 at 3:50 pm

  Test duration is either predetermined based on the window of time you are trying to simulate like the first four hours of a workday where you experience the first uptick in user activity and the downtick going into what is commonly lunch time. Or the test will run in the timeframe needed to achieve a certain transaction target, for example 100 shopping bag transactions every 10 mins on an e-commerce site.

• Administrator // Dec 20, 2009 at 3:54 pm

  Measuring the vusers in the test is a common monitor in the controller, calculating the number of vusers to use is a calculation based on a few factors such as the time it takes to perform the transaction in question and the length of the test duration.

• Administrator // Dec 20, 2009 at 4:00 pm

  Target load is derived from conversations with the client based on their operational history or targets agreed on based on the goals of the system implementation.

• Administrator // Dec 20, 2009 at 4:04 pm

  The documentation for the transaction mix is built by the performance test team, I use a number of excel spreadsheets to calculate out the transaction mix based on multiple inputs around total transaction time, known number of users in a specific use case and the target transaction rate.