Most errors in long-lived software occur in code areas that change a lot. To do things right, you have to make sure that no important changes go live untested. Test Gap analysis helps us to find untested changes.
After an introduction to Test Gap analysis (TGA), hear what we learned using TGA with customers and in our own development for more than 10 years and discover the answers to the following questions:
In addition, see best practices and useful KPIs in continuous use and the results of a cost-benefit analysis from many years of service at Munich Reinsurance Company. The workshop brings together several lectures that have received Best Presentation Awards at the German Testing Day, the Software Quality Days and the QS-Tag in recent years.