When it comes to building and deploying applications, one increasingly popular approach these days is to use microservices in Kubernetes. It provides an easy way to collaborate across organizational boundaries and is a great way to scale. However, it comes with many operational challenges. One big issue is that it’s difficult to test the microservices in real-life scenarios before letting production traffic reach them. But there are ways to get around it.
Loadero is a SaaS (software as a service) for testing web applications and our main target is to provide a powerful tool to our users, so they can create load tests, performance tests, and WebRTC tests for their needs. But sometimes a proper tool is not enough to execute tests: some companies don’t have enough manpower, others might not have enough expertise in the QA field, yet testing is required for every web application.
We are going to explore whether Load Test Driven Development is an idea that would be worth pursuing for your organisation. We will recap on what Test-Driven Development (TDD) is in the next section but fundamentally Now when you think about this, does it make sense to try and run a performance test before we have developed any code? We think it does and we are going to explain why. For clarity we are not suggesting that Load test Driven Development should replace TDD but rather to compliment it.
CPU or Central Processing Unit is the brain of any computer and its main responsibility is processing all the tasks required by the running applications. CPU Utilization is a key metric in performance testing which measures the percentage of time the CPU spends executing a task. One of the most crucial tasks to do when running a performance test is to monitor the resource utilization.
In this blog post we use podtato-head to demonstrate how to load test kubernetes microservices and how Speedscale can help understand the relationships between them. No, that's not a typo, podtato-head is an example microservices app from the CNCF Technical Advisory Group for Application Delivery, along with instructions on how to deploy it in numerous different ways. There are more than 10 delivery examples, you will surely learn something by going through the project. We liked it so much we forked the repo to contribute our improvements.
Have you ever wanted to load test an application behind a corporate firewall? If so, you probably ran into a few issues. Load testing on the cloud can be the most cost-effective way to run a load test, but not if the application isn't publicly accessible. Recently, we released a new feature for k6 Cloud that allows you to run load tests on your own private load zones. But first, does it really matter where load is generated from?
In the busy month of March, we finished working on the development of some new features for Loadero, two of which were requested by our valued customers. Work on some of the features started quite a long time ago and is finally finished. We are proud to share the news about our tool, here is what we got for you this time.
In this load test tutorial, you’ll learn how to use Postman for small-scale API testing. You’ll also learn about some shortcomings and challenges of the framework that can be solved by using a tool like Speedscale. Because HTTP services don’t have a graphical user interface, you’re forced to test web APIs by simulating requests from a known client so that you can control the traffic data.
In last week's office hours, Nicole and Paul sat down with engineering manager Marko Pandurovic to discuss the ever-evolving k6 backend. All systems turn more complex with time, and the k6 backend is no exception.
