BlazeMeter introduced a new continuous testing- as- a- service platform, which is designed to help development teams shorten release cycles.
The company joined forces with Sauce Labs to deliver the new platform, which enables developers to create and run tests and integrate testing into the existing development environment. As software increases in complexity, the number of required tests grows exponentially. However, testing is often still executed by people in different departments using different tools. Testing has long been a complex and resource- intensive process with a workflow that is time- consuming and difficult to maintain. The current process often results in inadequate testing, poor software quality and increased time to release.
BlazeMeter says it has broken through these barriers and can support dozens of engineering teams producing, integrating and deploying code continuously, without compromising software quality.
Alon Girmonsky, founder and CEO of BlazeMeter, said the ongoing shift in the industry is forcing developers to adopt agile continuous deployment and integration methodologies and move from perpetual to subscription-based solutions to keep up with the pace of the development cycles.
“Our open source and cloud- based testing platform helps developers facilitate continuous testing as part of the product delivery cycle,” he said.
Automated testing is now a critical part of continuous delivery pipelines, noted Steven Hazel, Sauce Labs’ co-founder and chief product officer, in a statement. “Combining functional testing from Sauce Labs and performance testing from BlazeMeter gives software teams a modern testing platform capable of meeting the demands of continuous delivery.”
BlazeMeter’s performance and Sauce Labs’ functional testing platforms support reading scripts and running tests with DevOps– friendly open-source tools such as JMeter and Selenium, and languages, such as Python, Ruby or shell scripts. The testing solutions provide libraries and APIs to create “homegrown” tests using common domain specific languages (DSLs).
Other key features include the ability to create and run tests with an API and with different provisioning. For example, a developer can run a module test from behind the firewall with local resources. On production, the same test can come from multiple geographies from the public cloud with or without load. When a test configuration is executed in an environment, such as a development environment, pre-production, post-production or other, it can easily adopt a different provisioning scheme. The testing-as-a-service environment can also be integrated with existing reporting tools in the continuous delivery cycle.