I have got following problem statment for one of my project
Problem Statement: Application should support 1000 users concurrently
Can some one plase help me to understand following information from above load Test requirment.
菱ow to decide the load Test duration for new and old application
標hat criteria we should to Use to decide the Ramp Up and Ramp Down
標hat is harness test
標hy we need warm up test
標hat concurrency and simultaneously users different
標hat are Important matrices before starting and Load Test activities for Planning the test
> How to decide the load Test duration for new and old application
Unless they have specifically asked for long-term tests, we run most load tests for about an hour. But the duration (and the ramp profile) is guided by the duration of the test scenarios. Short scenarios can be tested in less time than long scenarios.
> What criteria we should to Use to decide the Ramp Up and Ramp Down
Start small and work your way up. There is really no way to know how much load a system can handle unless you've already tested it. For your requirement, I'd probably start at 100 users and add 100 at a time up to the required 1000. But if the system performs poorly at 100, you'll want to back off to a lower start/increment to get more useful results.
> What is harness test
Typically this means running the test from within an automated test harness, but I've seen the term used in other ways as well.
> Why we need warm up test
This is most commonly used to populate caches within the app server, web server, database, etc, when a system has just been rebooted. It is not uncommon to see systems perform very poorly for the first few minutes and then improve as these caches are filled.
> What concurrency and simultaneously users different
For the most part, these terms are used interchangeably.
I wish you luck - that you are able to learn a lot from this project, maybe even uncover some performance issue(s) that can be fixed. If you are really lucky the site will go live and support the load w/out any error attributed to your testing or lack thereof.
What really got me to post a reply though is your request for standard formulas. [img]/images/graemlins/confused.gif[/img] This indicates that you have done almost no research and/or gained no understanding of performance testing or testing in general. There are essentially infinite possibilities. The infrastructure/technology, the application/functionality, user profile, and on and on and on.
We look forward to more detailed and thoughtful questions after you have done some research. [img]/images/graemlins/laugh.gif[/img]
P.s. you question regarding concurrent vs. simultaneous users may indicate you are using Load Runner (as I've personally not heard of a distinction, though a few possibilities come to mind) so maybe you should google that
A problem is a difference between what is perceived and what is desired, that
we want to reduce (Dewey 1933)
To define the scenarios is very important identify the business requirements.
Both functional and nonfunctional requirements.
With this information you will have answers to all questions and you can set settings that allow you to achieve the objectives defined in the master test plan.
In the test plan must be clearly defined criteria for success and failure of performance tests.