mabl today added load testing capabilities to its portfolio of application testing tools available through its Software as a Service (SaaS) platform.
This feature makes it easier to streamline testing within DevOps workflows by allowing load testing tools to measure application performance alongside existing mabl tools accessible through test automation platforms. Become.
mabl CEO Dan Belcher says the goal is to make it easier for developers to perform functional and non-functional testing as early as possible in the software development lifecycle.
It’s not clear to what extent testing responsibilities are being delegated to developers, but the easier it is to run these tests, the more likely they are, Belcher said. One of the core problems plaguing application development today is an inadequate level of testing. He added that the main cause of this problem was that it took too long to create and run the relevant tests.
mabl streamlines the process of creating and managing test processes with a test automation platform based on low-code tools. These tests can be configured to run independently or integrated with DevOps pipelines, he said.
Offloading testing to developers doesn’t eliminate the need for a dedicated team of testers, but it should reduce the number of day-to-day errors that occur. The reduction should free up those development teams to focus more time and effort on more complex quality assurance (QA) issues, he said.
Of course, as artificial intelligence (AI) continues to evolve, more and more testing processes will be automated, so most organizations will soon find themselves revamping those processes. In theory, SaaS platforms that aggregate test data should be better positioned to apply AI models to testing. This is critical as the pace of building and deploying more complex applications shows no sign of slowing down.
In the meantime, DevOps teams should assume more responsibility for security issues that arise after an application is deployed. It may take some time, but the number of legislative initiatives specifically focused on application security is increasing. It’s only a matter of time before laws are passed that impose security responsibilities on organizations. At the same time, application software consumers are becoming less tolerant of problems caused by minor mistakes, such as SQL injection attacks. Application testing is expected to be much more thorough than in the past.
The problem, of course, is that too many development teams tend to view security requirements as obstacles to overcome, rather than as an essential part of the QA process that ensures that expectations are consistently met and exceeded. is.
At this point, it’s clear that the application will be better tested. The only thing you have to decide now is how much friction you will experience in the process of achieving that goal.
