For all you Jenkins users out there, here's a guide on how to integrate k6 in your Jenkins Pipline setup.
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!
You and your team have been pushing plenty of updates to your app over the last few weeks in preparation for a marketing milestone.
Everybody in the company is excited, and you can’t wait for users — and potential customers — to see what you’ve cooked up for their enjoyment.
But you haven’t been continuously performance testing throughout development (a bad move, but we forgive you), and you just realized it’s time to start running load tests.
Never fear! We’ve broken down a few steps to get your load testing extravaganza up-and-running, and from there you can smoothly transition to continuous testing, which will save you from this headache in the future.
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
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.
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.
In part one of this series, we started defining the problem we are solving. Essentially, we are trying to leverage Docker and DevOps tools to ensure our decentralized team can release faster and with less centralized synchronisation. Before we dive into software choices, we have to talk about the elephant in the room.
Tl;dr — Load Impact is growing, and one of the challenges with growth is making sure your infrastructure and development cycle mature with that success. This is Part 1 of our series, “The Road to Microservices.” Here’s what we’ll cover:
- Why we decided to make the change to a microservice-oriented approach
- We’re switching to Docker! (Isn’t everyone, at this point?)
- What we expect to get out of these changes