The latest News and Information on Software Testing and related technologies.
It’s no exaggeration to say that today’s internet is built on JavaScript. Around 95% of all websites have been built using the language, according to the latest figures. JavaScript has evolved beyond the client side and is now used to construct entire technology stacks, not to mention support databases like pouchdb and RethinkDB.
The device landscape is as vast as it is complex. With at least 63,000 possible device profiles reported—a number growing at almost 20% per year—the scale of device fragmentation is staggering. New models, operating systems, browsers, screen resolutions, etc., make it extremely difficult for web and app developers to deliver a consistently flawless user experience across all combinations.
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.
