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...
Lisa Waugh
Lisa Waugh is an exceptional Software Development Engineer in Test and DevOps, passionate about quality and innovation, and currently a Testing Engineer Lead at IBM. She brings over 30 years of experience in information technology, with concentration on DevOps, Continuous Testing, and Performance Testing. She has a diverse background in multi-platform hardware and software technology and extensive technical experience in cloud, workstation, mainframe, and client server environments. Lisa is primarily involved with automating continuous testing pipelines to include performance, load, and system testing, identification of potential performance issues, and performance tuning of cloud microservices.