It’s been a while since we published our latest product updates, but the work on Loadero wasn’t paused. Our team was busy working on the newest features to make your performance testing with Loadero more convenient and effective.
When developing web applications, one of the important things is to provide smooth accessibility of your product to the clients. But that is not an easy task to accomplish as several factors come into play. Software testing requires coverage of many different devices, environments, and conditions. We in Loadero provide features to use different browsers, run tests from different locations, set different fake media for webcam and mic simulation, etc.
There are various reasons for running Python browser automation tests locally, the most common one for us is saving time. Loadero test runs usually take no more than 5 minutes to initialize and start execution but can reach up to 10 minutes or more depending on how busy is the test run queue. To increase the speed of development, it’s often quicker to create the test script on your local machine and then run tests on Loadero.
April was a busy month with some significant improvements made to Loadero. While most of them aren’t really visible in the tool itself, they make Loadero work better and allow to use it even more efficiently. Here’s a list of the main updates in Loadero this month.
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.
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.
