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.

How do you manage to release often without major issues? Create a checklist for your software releases, a list of steps to blindly follow every time release a new piece of software. Here is an example of what steps your list should contain: This list can go on and on, by I would suggest that every team should have a similar checklist. This checklist should be reviewed and updated every 1-2 weeks (doesn’t matter if you do Scrum or Kanban), most likely at the team retrospective meetings.

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.