We have created a simple step by step guide on how to integrate k6 in your TeamCity build setup.
The concept of load testing seems simple. You just run a test against your app, API or site and see how it performs under a simulated user load. But the reality is slightly more complex. There are three load tests you must run to optimize performance.
For all you CircleCI users out there, we have created a simple step by step page on how to integrate k6 in your build setup.
For all you Jenkins users out there, here's a guide on how to integrate k6 in your Jenkins Pipline setup.
As some may already know, Load Impact recently let loose upon the world yet another load testing tool - k6
As we’re big believers in dogfooding we’ve used our open source load testing tool, k6, to set up load testing automation with CircleCI. This is how we did it, and some tips and tricks to make your load testing automation easier. Let’s go!
Tl;dr — We're hosting a DevOps Stockholm meetup at our HQ in Stockholm. The headline of the event is "How to load test, the developer way" by Robin Gustafsson.
This webinar not only shows you how to automate load testing in your CI pipeline, but you’ll also learn how Julien applies Microsoft’s best practices to the DevOps and “continuous” mindset while embracing the world of open source software.
Continuous load testing throughout the software development process improves your understanding of your website, application and infrastructure performance.
Developers around the world are discovering that load testing isn’t just a one-off project or something you wait until the last minute to do.
Integrating load testing into your DevOps and Continuous Integration lifecycle helps you achieve a few things.
- Load testing is yet another task you can automate — and we know that’s a good thing
- Understand the performance impact of each code commit
- Plot your app or website’s performance trend over time
Performance testing is often mistaken for performance tuning. The two are related, but they are certainly not the same thing. To see what these differences are, let’s look at a quick analogy.
Most governments mandate that you bring your vehicles to the workshop for an inspection once a year. This is to ensure that your car meets the minimum safety standards that have been set to ensure it is safe for road use.
A website performance test can be likened to a yearly inspection — It ensures that your website isn’t performing terribly and should perform reasonably well under most circumstances.