Quote:
Originally Posted by muttiah
You're not gonna discover the issues you want to test with automation until lots of people actually use the system.
Not true in our case. I suspect its rarely true but I guess its one of those it depends/YMMV issues. Every time I've done load testing I've learned tons of valuable information.
Quote:
Originally Posted by muttiah
How big is the company? Live fire in house testing is a pretty good and very cheap method. Just get bunch of people to logon at once. We do live fire tests before every release. Our software is different though. The stress doesn't come from many users. It comes when a few users simultaneously make extremely computationally expensive queries.
We're small so this isn't really an option. Although we have a small number of users its just not quite the same.
I think in a lot of cases load testing isn't necessary - but when you have a specific point in time that you know is going to really increase load and increase attention to your site I think its important to make sure you're not going to fall over*.
The beauty of a good load testing suite is that even in cases like you're describing (few expensive operations) you can simulate that and see how your overall performance degrades. It's probably nice if you can serve your "simple" customers well even when your "complex" users are experiencing performance problems.
* See the stories about the Romney campaign's 'app' disaster. That's a perfect example of an application that needed thorough and automated load testing.