Systems | Development | Analytics | API | Testing

Previously Loadero had the same amount of compute power assigned to each participant in every test, but applications that our customers test are different and have different demands for end user machine resources. That is why we added compute units to give our customers better flexibility in test creation. This also allows to run much larger load tests as well as optimize cost of running the tests for the applications that don’t use much compute power.

Leaving movie quotes aside, load testing helps you understand how your application behaves under both normal and peak conditions, and discover what is causing the degradation. But truly, the main goal of load testing is not to lose customers. You don’t do load testing for the sake of doing load testing.

It’s so easy to record a load test for your website, just add to Chrome Browser the JMeter in the Cloud Chrome Extension and you’ll be able to record and run a load in less than 60 seconds. Let’s have a deeper look how to do this. This is it, less than 60 seconds to record a load test. Now you can: More detail can be found in this video. Written by Bogdan Vazzolla.

Testing is a critical step if you want to ensure quality in your products. It’s crucial to test your applications to make sure they work properly – otherwise, customers are less likely to buy or continue to use them. While important, software testing can be a repetitive process that takes time and resources you’d probably rather use for tasks that deliver innovation to the functionality or performance. This is where test automation comes in.

A product manager’s job first and foremost is to deliver value to their customers with the products they oversee. In order to ensure quality, those products need to be tested. Testing before release in a well thought-out manner gives product managers the confidence to create and execute high quality products and user experiences.