response time

 

use 90%, not average (90% is where most people will be)

 

complicated automation

 

needs to be programmed

lost of detail on randomization of parallel request streams

use minimal Ruby code to create test drivers and reports

most tests... just use production monitoring tools

uses real-time character output to watch tests running

 

 

scaling

 

if you can bring down your site with one computer, you're already screwed

need a cluster

use UDP packets, can be broadcast, stateless

...tuned out...

 

user testing

use Google analytics

write scripts for each page

simulate production environment in test environment