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...
Sachin Avasthi
Senior Technical Staff Member
IBM
Sachin Avasthi is a Senior Technical Staff Member in IBM's CIO organization where he focuses on Application Modernization and helping teams assess, identify, and implement a plan to modernize their application. He also works with IBM Research to co-create tools that can help accelerate the modernization journey and scale the use of these tools. During his career, Sachin has been a software developer, a DevOps evangelist, and an architect. He has a passion for researching emerging technologies and implementing them in a real-world use case in an enterprise application landscape. Outside of the day-to-day work, he spends a lot of his time mentoring developers and architects on career and professional development.