ISSUE #48 - February 25, 2018
Tester’s Digest is back after a flu break. We look at the classical QA task of load testing, with some modern twists - should developers do it? should you load test in production? how can it all go wrong?
Should developers write their own load tests, rather than have QA or another team do it for them? This post votes yes:
How you can write load tests wrong: 1) make them too short; 2) ignore anomalies; 3) reuse test data (or rather, fail to disable caching); 4) only load test under happy path conditions with no failures.
Additional uses of load tests: to help reproduce a sporadic performance issue, or to uncover app slowness based on user’s location.
Load testing of websites with Vegeta tool and test data in a Python Pandas dataframe:
Website Speed Test tool, built on top of the well known WebPagetest, analyzes load time of images on your website and makes improvement suggestions, complete with optimized images you can download and use:
Open source tools for load and stress testing (Fiddler, JMeter, Locust, Taurus, Gatling, Siege and more):
On different ways of setting up a load testing environment, from testing in production to rolling your own:
Worth learning: Introduction to distributed systems. Per Lamport, 1987, “A distributed system is one in which the failure of a computer you didn’t even know existed can render your own computer unusable”. These days, there is no other kind of systems…
If you received this email directly then you’re already signed up, thanks! Else if this newsletter issue was forwarded to you and you’d like to get one weekly, then you can subscribe at http://testersdigest.mehras.net
If you come across content worth sharing, please send me a link at firstname.lastname@example.org