Posted on

Don’t Give Up Yet… Keep-Alive!

We founded StormForger Load and Performance Testing SaaS in 2014 and while much has changed since then, one thing hasn't. 

HTTP is with its 24 years a well-aged fellow among the web protocols.¹ Today we are mostly using HTTP/1.1² or HTTP/2 and if you have fully embraced the new HTTP/2 world in your entire system this article is mostly an anecdote of past issues. But HTTP/1.1 is still alive and kicking for many systems. And even given its age, people are still forgetting about a very important feature that previous versions did not provide: keep-alive.³

Posted on

Why Is Load Testing Significant?

Image titleLoad Testing can monitor the response times of the system for every single transaction during a set period of time. This kind of monitoring can bring significant information, precisely for stakeholders and business managers, who look for conclusions based on these outcomes, along with any data for supporting these findings. Such type of testing can also raise attention to any complexity and issues in the application software and fix these performance bottlenecks before they become extra problematic. As a developer or QA engineer, one can possibly incorporate several kinds of tests into the code checking: integration tests, unit tests, UI tests, and more. Load testing supports testers or engineers to understand the behavior and accessibility of the application. It critically tackles the following queries:

• Do the codes show the desired performance?