Maintaining API test cases across multiple environments, for different load levels, and types of tests (eg. smoke, functional, regression) traditionally required separate tests be written and maintained. Test maintenance is expensive. If you have three lower environments that tests are run for, then you usually have at least three different tests you are trying to keep in sync. If you have a new API added for a microservice, then you have to modify and validate across all three tests at a minimum. If you are running different load levels for build tests verses load tests, for example, that...
Shailaja Patel
Principal Automation Engineer
IBM
Shailaja Patel is a Principal Automation Engineer with the CIO office of IBM. She comes with a demonstrated history of working in the information technology and services industry. Skilled in Business Automation & Test Automation strategies, Shailaja also provides guidance to teams on various facets of automation. She brings over seven years of experience in information technology, concentrating on automation, DevOps, continuous testing, and performance testing. Prior to joining IBM in 2019, she held test automation roles for multiple clients of Accenture in India.