When “shift happens” – shift left for functional API testing
Introducing CA BlazeMeter API Test
The age of agility and continuous “everything” has brought us faster developed and deployed apps, more creative features and the development of advanced technologies. These headways are achievable by “shifting left” of traditional downstream processes such as testing and deployment “as code”. But to the developer, that needs to understand the requirements, develop and test the features, document, possibly create videos and define deployment rules, that’s a lot of “shift”. So when “shift happens” what can be done to alleviate some of the work? Automating tests. And not just automating any tests, but automating API testing.
Automated API testing is the only way to properly do agile and continuous testing. Automated UI testing is just too brittle. Every time there is a UI change, the tests breaks and then the automated test has to be recreated, thus slowing down the entire process. However, despite the importance of API testing, that will continue to grow in importance as the Internet of Things, containerization and microservices become more far-reaching, API test creation is still a manual process.
We understand that API testing needs to be automated, but creation of the tests are not. Developers / Agile Testers are expected to think of, create and run all possible API pass-fail scenarios (which if we are honest doesn’t happen). As if this isn’t challenging enough, they are required to do so within the two week sprints where they have a lot of other “shift” to do that we already mentioned. Finally, they need to do so each time their APIs change.
Introducing CA BlazeMeter API Test. It only makes sense that in an automated testing world, API test creation should be automated as well. CA BlazeMeter API Test can automatically generate and execute functional API tests and provide drill down reporting with trending. BlazeMeter API Test creates a comprehensive set of API tests that enable developers to focus on developing and fixing issues, which is what they do best, rather than trying to come up with the proper tests to validate their APIs.
The SaaS-based solution delivers API testing that automatically creates hundreds of API tests to validate a single API, including positive, negative, edge and SQL Injection tests. API definitions can be uploaded from Swagger specs, manual creation, and imported from APIM tools, and imported by R/R Pairs (coming soon). The tests are automatically created and then executed concurrently either on-prem or in the cloud. As expected these tests can be executed through their own APIs allowing them to be part of a CI/CD process. Reports and results are clearly presented and can be shared among team members.
CA BlazeMeter API Test also helps companies to finally perform continuous testing. Automating the creation of automated tests is the only way to have true continuous testing. Whenever you have to stop and re-record, or rescript a test, that stops the testing process and therefore it is not continuous. Developers can even take the functional tests and run them as performance tests through CA BlazeMeter. The reuse of tests is yet one more part of continuous testing.
There is now no reason to assume release risk around API testing – so don’t take any “shift” unless you’re shifting left.
Come see us at Velocity
Attending the Velocity conference in San Jose and want to learn more? Stop by the CA Technologies booth (#901) for a demo of CA BlazeMeter API Test and/or join me at my session Continuous delivery made easy: Removing barriers in the modern software factory on Wednesday, June 21 at 11:25am PT.