Systems | Development | Analytics | API | Testing

Comprehensive software testing has never been more important than it is today. Software will continue to play an essential role in our daily lives. What is changing – and will continue to change – is what we test and how we test it. Modern software codebases are immensely complex. It’s simply not feasible to execute all of the necessary test cases manually. The bulk of testing today is automated.

Year after year, DevOps industry reports and practitioners in the field point to testing as the biggest bottleneck in the software development lifecycle. Take GitLab’s 2021 Global DevSecOps Survey – for the third year in a row, the majority of respondents pointed to testing as the biggest cause of delays. That’s a lot of finger-pointing. If we had to guess, testers are tired of it.

In the era of digital transformation, misalignment between the business leaders steering the overall strategy and the technical experts who build, implement, and maintain solutions is one of the top blockers to a successful sea change. These groups need to be able to collaborate to define what each solution requires and the why behind it.

We are sure you've heard of Exploratory Testing, and you've probably heard about how amazing it is. (Yes! This is the weapon of choice!) And you may believe you know all of it. You're doing it, your team is doing it, therefore everything should be OK; according to the great book of plans, you're all set.

When using a testing tool, it is only logical to trust its results. And the more well-known the tool is, the more trust we put in it. Furthermore, how could we know it is wrong? After all, who is in a position to judge the judge? This phenomenon is particularly true in the load testing community, since the field is still something of a niche among the testing world. Finding deep-dive studies about the actual technical aspect of load testing is difficult.