Believes in a holistic approach to software development, that’s why testing and quality assurance are only a few elements he’s interested in. He likes to automate not only tests, but also any mundane and repetitive work that gets in the way of his team. Despite 10+ years of experience, he still loves to continuously improve and experiment with new approaches, ideas and tools. He has an allergy to blindly following processes.
Currently works at Wizards of the Coast as Lead Quality Engineer, where he leads a team of Quality Engineers helping in creating official digital tools to play Dungeons & Dragons – D&D Beyond.
Small-scale load testing – succeeding while failing
Before releasing a new large feature of our platform to our users, it would be wise to check (among many other things) how well it works when all our users decide to use it at the same time. There are various types of performance tests that we can perform to verify that, using a myriad of tools already available on the market so that we can devise the greatest test plan ever. But then, reality hits with well-known phrases like ‘deadline’, ‘reducing scope’, ‘cutting corners’ etc. and everyone forgets about that and just tries to get stuff done. Millions of users do not care about that and will still generate the same traffic – what can we do in such a situation?
I would like to tell you a story of our performance testing efforts around the launch of our latest product and how we had to adjust the plan due to ‘dynamically changing circumstances’. I’m going to talk about the journey we went from our starting approach and the types of tests we were supposed to conduct, to the scarce testing we had room for in the end. All that while introducing a new tool, K6, and testing a first-ever within the product system backed by Kubernetes, with both REST API and Websocket communication.
In comparison to initial plans, our final efforts seemed like a failure, but we still managed to reach great conclusions and discover and fix a few issues that could have resulted in catastrophic failures.
Język prezentacji/Language: PL/EN