| || |
Load life cycle
This is another try...
In my company we are trying to figure out what is the "correct" life cycle of load testing (when should we start benchmarking, when to perform load test, what are the criteria for starting each phase and exiting the stage, etc...)
Please share with me any knowledge you have in the field. (or any good link...)
Re: Load life cycle
My best attempt at "quantification" is encapsulated in www.perftestplus.com. however...
I don't know that there is a "correct" answer. "As early as it provides value" is actually my best answer. In an ideal world, you'd model the potential software before any hardware decisions are made or any code is written, then a hardware decision would be made and you'd start by baselining/benchmarking that hardware, then the software that will reside on it (and likely tuning it based on the model) while the code for "build 1" is being written, then when "build 1" is dubbed "fundimentally functional" by the functional/system testers, you'd start with your load/stress/stability testing on that build. All the while helping developers build and analyze load/stress/stability tests at the unit testing level. Then iterate testing/tuning with each build until go live day.
This is obviously an ideal situation AND an oversimplification, but maybe it will help in some way, or spark a line of questions/comments that will be useful to you.