Performance testing is complex and takes time because it still requires human action. So how can reliable and thorough performance tests be executed in these fast-paced environments and how can performance testing tools integrate with a DevOps tool chain?
In order to secure the deployment of releases in production, the developers typically apply an early performance testing approach for the main components.
Most of them are more comfortable building performance tests directly from their IDE, while performance engineers use another way. As a consequence, it is not possible to re-use the work done by the developers.
We can overcome this challenge by building a strong “quality as code” pipeline mixing pure code scenarios for component testing, and hybrid design for your staging pipeline.
In this session, you will learn more about the best practices to include performance testing into your DevOps development process:
With 20 years of experience in software testing Wim has gradually evolved to a versatile generalist covering several aspects of testing. Driven by versatility and a great eagerness to learn new things he is always looking how and where he can stretch his comfort zone to deal with new challenges. It enables Wim to operate with a helicopter view as well as discussing about the details.
Henrik is Performance Engineer at Neotys, a leading provider of load testing software.
He has been orchestrating and conducting performance tests for over 10 years, delivering projects in all contexts including extremely large Cloud testing on the most demanding business areas such as trading applications, Video on Demand, sports websites, etc. Prior to Neotys, Henrik worked as .NET architect for Logica and Performance testing expert on large accounts in a variety of industries including insurance, car industry, retail and energy. Amongst the numerous initiatives he worked on, Henrik has built the performance Center of Excellence (CoE) handling load testing of all the European branches of a major insurance company.