The answer to the question above might seem easy!
Well, sort off. (I should say I'm going to write this site like a blog, as things come to mind, so please bear with me if it's a bit convoluted in places...)
I'll define 'load testing' as:
'running multiple users against an application, checking response times and long term stability.'
There are of course a lot more details and there are questions such as the aims, the benefits and
the value of even trying to do this. I'll try to cover as much of this as I can in these pages,
along with how to get started commercially, from a QA or Developer role.
Getting started on this as a full time job can be difficult, mainly because computer system
are necessarily complex and to do the job in a commercial environment, you do really need
experience in these environments and to know how things fit together. And that includes teams
of people, not just the machines. You need to be able to communicate with all the different teams
and know who to talk to about all sorts of different technical issues.
I will try to cover as much ground as I can within these pages. It is a bit trial and error, depending on what's on my
plate currently and how much free time I have to write it all up. Hopefully, this page will
become more useful over time.
Areas I want to cover
I want to build a tutorial here, not for absolute beginners, but for developers or technical QAs
who want to move into Performance Testing.
1. Code and languages used
2. Performance Testing applications, commercial, free and market leaders
3. Test data in theory and practice
4. What you need to know about websites (this tutorial concentrates on HTTP applications in the main)
5. Test passes and fails, SLAs and other requirements
6. Log files, trends and getting the data you need
7. Graphs, analysis sessions and management reports