Software Test Automation 2002: A Case Study In Automating Web Performance Testing

Key points from this presentation: define meaningful performance requirements; we're always searching for the maximum number of users, design bottlenecks, and performance tuning points; changing your site (hardware or software) invalidates all previous predictors; reduce the number of scripts through equivalence classes; don't underestimate the hardware needed to simulate the load; evaluate and improve your skills, knowledge, tools, and outsourced services; document your process and results so that others may learn from your work; use your new knowledge to improve your site's performance; and focus on progress, not perfection.