5 Load Testing Resolutions for 2018
5 Load Testing Resolutions for 2018
Learn about a few additional things that you should think about when load testing your website to achieve optimum performance.
Join the DZone community and get the full member experience.Join For Free
xMatters delivers integration-driven collaboration that relays data between systems, while engaging the right people to proactively resolve issues. Read the Monitoring in a Connected Enterprise whitepaper and learn about 3 tools for resolving incidents quickly.
This blog has covered many different tips and best practices for performance testing your website or app before big events, like Black Friday, the big game, and more. In this blog post, we want to offer you a few additional things to think about when load testing your website. Will these become your load testing resolutions for 2018?
1. Learn All You Can About Your Load Testing Tools
There are lots of great open source load testing tools out there, like Apache JMeter™, Locust, Gatling, and Grinder, just to name a few. But are you maximizing the options these tools can provide you? There might be features in these tools that fit the exact gaps you have when performance testing, which you might be dealing with today by ignoring or with complex workarounds.
This year, learn as much as you can about these tools so that you can work better, quicker and with a more satisfying experience. If you’re using JMeter, we have a great free JMeter academy, and here is a list of JMeter resources. For Locust, here are quite a few helpful articles.
We also recommend learning about other open-source tools. This will expand your horizons as to different load testing possibilities. Here is a good comparison of the tools. Don’t forget, they can all be easily run through Taurus, so you don’t have to learn a new tool if you want to use it (though you can). Soon, you will also be able to also run many of them through BlazeMeter.
If there are any open source topics you would like to learn about, let us know in the comments section and we will try to help by writing a blog post about it!
2. Contribute to the Open-Source Community
The open-source community has created wonderful, free tools that improved developer capabilities and gave DevOps a huge leap forward. The nice thing is that when contributing to open-source, you’re advancing the community and yourself by improving your technical capabilities and building your name.
There are many ways to contribute to the community. It can be as big as starting your own open-source project, and as small as answering questions on forums. In the middle, you can develop code, help with build management, do QA, write documentation, provide feedback, and create content. Every little bit helps, so give it a go this year.
BlazeMeter contributes to the open source community by developing plugins for JMeter and Jenkins, by creating content for developers and by creating Taurus, an open-source test automation framework.
3. Shift as Left as You Can
Shifting left is probably not a new concept for you. You, your team and your company have probably implemented shifting left and agile methodologies to some extent into your workflows. But if you still find yourself in a rush when you load test or upset about bugs that were found too late, you should take a step to the left.
Get your company resolution for this year to be to go agile as a team. You can mix up your teams and create agile ones, implement DevOps testing methodologies in your development process that include performance testing, start working in sprints, choose tools that enable agility and much more. If you work as a team, you can do it together. Because it won’t happen on its own.
When shifting left, you should also take into concern two expected trends in 2018. According to Dan Arad, BlazeMeter’s Product Manager, DevOps teams will be required to handle increasing network traffic, and security will become an even greater concern. “We may very well see more global security events than we’ve seen in 2017,” he says. Is this in line with your company’s products? You should definitely find out.
4. Mark Big Events on Your Calendar
Following up on the last point — you want to implement continuous testing but you also want to ensure that you are ready before big events. So mark any events that will require special load testing this year.
This could be events like Black Friday if your product is related to that, holidays, releases or even sprints. The point is that you have a calendar in front of you that marks when you are expected to be under pressure, you can plan accordingly. This will make 2018 more relaxed and content - which is always a good resolution.
5. Learn Containers
Andrey Pokhilko, renowned thought-leader and innovator within the Apache JMeter performance testing community and the founder of Taurus, sees 2018 as the year of containerization. As AWS presented its hosted containers infrastructure and containers winning the minds of developers, the operation side will massively migrate from machines and use containers infrastructures provided by giants like AWS, Google, and other players.
So, if you have no idea what Kubernetes is, how to use Docker or what containers are, 2018 is the year to learn! Start simple with basic terms, play around with creating your own containers, and follow infrastructure giants to stay updated with the newest products available.
2018 is going to be a great year! What are your new year’s load testing resolutions? Let us know in the comments section below.
Published at DZone with permission of Noga Cohen , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.