In the first installment of this mini-series, we outlined how you efficiently prepare for performance testing. In the previous article, we got into the nitty gritty of what tests to run, and how to run them.
The final step toward ensuring you’re shipping high-performance applications and websites is to continuously test throughout your software development lifecycle.
If you’re a DevOps-minded organization that’s already working with Continuous Delivery and Continuous Integration (CD/CI) tools, then you’re off to a great start.
You can go directly to our Performance Testing and Continuous Delivery page, and you’ll see we have ready-made integrations for some of the most popular automation software out there, including Jenkins, CircleCI and TeamCity.
For those who are using automation software not listed on that page or those who aren’t yet automating tasks, we pride ourselves on our clear and concise API documentation.Use the Load Impact API to programmatically trigger load tests whenever you and your team commits code.
Pinpoint Performance Issues Early
Continuous Testing means you’ll be able to clearly compare load times and overall performance before and after your development team makes changes and/or upgrades to your system.
We’ve also had users come back to us and say continuous testing has helped them identify performance degradation after changes that were not initiated by them — such as network or service provider changes.
Continuous Testing and performance monitoring is also a great way to make sure you’re spending the right amount of money on infrastructure and resource deployment.
While the majority of our users find they’ll need to spend more money on infrastructure after they start load testing, they do occasionally find that they can actually start spending less on server space!
Of course, every system is different, so it’s always a good idea to plan for this to go either way.
Happily Ever After
Literally all of your problems in life will be solved by including performance testing in your continuous integration. (*This isn’t really true, but your life will probably be easier when you automate the execution of load tests, and we can say for sure that you’re going to get useful data from your tests).
And there you have it. Those are the three phases of load testing execution as we see them. If you have any questions about performance testing or using Load Impact, please feel free to reach out to our Customer Success team anytime.
And if you haven’t already started testing — What are you waiting for?