Plan and execution of performance testing, for new .net product
I am looking for information on setting a plan and execution of performance testing. Performance testing is not a small task by far, currently management want us to use a stopwatch on our .NET product. Our QA department is all new (3 people including myself), we are modifying the approach to use automated tools rather than a stopwatch, and also we are all new to performance testing.
1. Can anyone point us to websites with .NET acceptable response time information?
2. Is there a website with information on setting up a performance test plan?
Re: Plan and execution of performance testing, for new .net product
(shuddering, shaking, despairing in reaction to management)
How many concurrent users? The answer to that may help relieve my symptoms if the quantity is small. More importantly, adding details to what you are asking should help get you some robust answers from the group here.
To quote you: "Performance testing is not a small task by far"... You have mastered the most important part of performance testing. I applaud you.
1. This is more up to your customer's needs, service-level agreements, and/or system specs.
2. You are at a great website for information relevant to what you seek. There are also links embedded in the topics here that point to some really good resources. Please become acquainted with the advanced search to your upper right. Use key terms in the text box and select this forum from the list of forums.
Help out fellow respondents here by providing information about:
1) How many concurrent users,
2) Stress, load, endurance test etc. (Those terms are defined within this forum)
3) What are some the questions that people want answered about performance of your architecture? (Key piece!)
BTW - inform management that performance test engineers typically use "industry-standard" Rolex watches, in order to attain the necessary precision. [img]images/icons/smile.gif[/img]