The shift in development styles to rapid deployment (rapid app development) has been great in many ways for developers, for devops and for business. You’re likely implementing continuous integration and continuous delivery in as many places as you can. Or your CI/CD imperatives have come down from management.
No matter why you’re developing your projects faster, the fact remains that you are, and that the speed of development isn’t slowing. The pace of business demands it.
Thus, the new development paradigm is rapid deployment, and projects have to get done faster than ever before. Yet as developers, we know that no matter how great the benefit of a particular technology or methodology, there’s always a downside.
In this case, rapid deployment can mean more bugs or errors creep into production. No-one wants to ship bugs. But the faster we ship our apps and sites, the more likely we’ll ship some errors in code.
Reduce Risk With Testing
Unit testing is great - and it should be uniformly adopted as part of your development pipeline.
What’s unfortunately often overlooked is load testing. Code coverage is great - but can your rapidly developed app (and its infrastructure, DevOps folks) stand up to its expected use? Can your site handle the expected traffic?
That’s where load testing comes in. We recommend that you load test both consistently and continuously.
Continuous Load Testing
Why do we say continuous? Well, we mean “continuous” in the same sense as in “continuous delivery,” “continuous deployment,” and “continuous integration.”
Continuous and automated testing is part of each of these (CI, CD, and CD). This automation focuses on functional testing, yet we recommend you not overlook load testing. Continuous load testing includes load tests in every build cycle. We recommend basic load tests along with daily builds. These basic load test thresholds can help you catch minor issues before they become major ones.
Consistent Load Testing
So in addition to continuous load testing, we also recommend consistent load testing. It’s easy to let performance testing and load testing slip when you’re focused on shipping.
Yet they must be consistently tested, not just before you expect a bunch of traffic or at the last minute. Consistent load testing means doing more than occasional load testing.
Consistent load testing means you’re catching potential performance killers before they become problems. It means you’re not caught by surprise when traffic peaks hit. And it means you’re a professional developer testing as much as you can while you have to ship more, faster.
Good luck with your risk reduction with load testing, and, as always,