This document discusses web performance testing and provides recommendations for establishing a performance testing culture. Some key points:
- Performance testing is important for evaluating how a website or application will perform under load and identifying bottlenecks. It should be done continuously from development through production.
- Metrics like response time, throughput, error rates should be monitored across loads. Problems may indicate scalability, capacity, or reliability issues.
- Tools like JMeter and Jenkins can be used to automate performance testing and integrate it into continuous integration/delivery pipelines. This allows testing at different stages and "shifting testing left."
- Real user monitoring provides insights into user behavior and key metrics that should inform realistic performance testing models and goals
Related topics: