I am looking for a couple of definitions of "bounds checking", "load testing", and "stress testing". My boss says that she is looking for an application for bounds checking, and I want to make sure that's really what she is looking for.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by JLHedges: I am looking for a couple of definitions of "bounds checking", "load testing", and "stress testing". <HR></BLOCKQUOTE>
Load Testing is comprised of multiple terms and types of tests. A simple Load Test (one user scenario) is the lemming principle (how many concurrent connections/users can get onto a system at one time before the SUT fails). This usually involves the "All at Once" approach or the continous ramp to breaking point approach.
A Performance Test is how well certain pieces of the SUT perform/respond under load (a few user scenarios in the same functional area or not). This relates to page times, dB lookups, CPU utilization, etc. of the like. At what load level do you see degradation or failure. You ramp to a specific level and record the performance at top ramp point.
A Stress Test is running the load test over a specified period of time (12 hours for example) to place a continous load upon the SUT (multiple user scenarios run repetitively). You want to see how long you can go before you break/fail. You ramp and run at steady state for the test period.
A Scalability Test is a combination of the previous two load tests. You look at performance of components of the SUT over time and a different load levels (multiple user scenarios with different mix ratios of scenario type and virtual users). In the end you do comparitive analysis to determine optimum performance (or optimum failure).
Bounds Checking could mean the literal term which would apply to the application itself. Using a tool to bounds check on data types and the like. There is a tool called "Bounds Checker", it is a product from Compuware (NuMega division).
Product info: "BoundsChecker provides clear, detailed analyses of programming errors, many of which are unique to C++ and detects and diagnoses errors in static, stack and heap memory, and in memory and resource leaks."
If this is not correct then maybe they mean bounds checking to be Scalability Testing.
That has been my experience with this type of work. Hope this helps.
[This message has been edited by jimhazen (edited 11-23-2002).]