BlazeMeter has launched an approach to continuous testing that enables developers to run tests on application code whenever they want to by invoking an API. Combined with functional testing tools from Sauce Labs, the BlazeMeter approach to testing makes use of libraries and APIs to create “homegrown” tests. Invoking the BlazeMeter API can make both the creation and running of tests highly automated.
Ophir Prusak, senior vice president of digital marketing for BlazeMeter, says the company’s namesake testing platform makes use of open source software to reduce the cost of testing while making it simpler for developers to embed testing directly within the development process.
Prusak adds that BlazeMeter makes it simpler to test different snapshots of code releases in addition to combining different test configuration fragments into one configuration. It can also granularly define test result thresholds with pass/fail results that get saved in XML format. As a result, that information can be shared and consumed by a wide variety of DevOps platforms, he says.
IT organizations, says Prusak, now have the option to deploy BlazeMeter in a public cloud, on premises or in a hybrid cloud computing scenario that can be managed via a central console. Rather than running tests after code is developed, Prusak says, IT organizations need to make testing a more integrated part of the application development process. This approach will not only yield higher-grade code, it should reduce the amount of time it takes to fix bugs and errors at the end of the application development process.
Prusak says that many IT organizations find themselves locked into testing platforms that don’t readily adapt to changes in the application development landscape. With its open source software, Prusak says, organizations will not have to worry about getting locked into a proprietary testing framework.
As software development in general becomes more agile, the amount of software being developed has increased exponentially in recent years. Prusak says that testing tools that were created to deal with the pace of application development based on a waterfall methodology don’t allow developers to create custom tests simply by invoking an API.
There’s still a lot of debate over the merits of agile versus waterfall methodologies when it comes to application development. But the one thing that just about everybody agrees on is that the sooner a bug is discovered in the application development process, the less costly it generally is to fix.