Team-Driven Microservice Quality Assurance

Quality assurance of a 200+ microservices system can not be centralized but needs to happen within the team, utilizing its expertise and creativity

While the Microservice architectural style has a lot of benefits, it makes certain QA practices impractical: there is no big release candidate that can be tested before put to production, no single log file to look into for root cause analysis and no single team to assign found bugs to. Instead there are deployments happening during test runs, as many log files as there are microservices and many teams to mess with the product.

At REWE digital we took a strictly team-driven QA approach. Our teams tried a lot of good and bad ideas to QA our microservice ecosystem. This involves automated testing, but also monitoring, logging and alerting practices.

In this talk I will present some of the best and worst of those ideas and explain how we try to implement a minimal QA alignment.

- – - – - – - – - – - –

Get access to the slides here:

https://slides.com/mkutz/team-driven-microservicequality-assurance


Related Sessions


  • Tutorial
  • Keynote
  • Talk
  • Workshop
  • Combo
  • Bonus
  • Active
  • Social

150-min Workshop

14:25-17:25 Room D5+D6 - Track 7: Workshops

Git for Testers

Equipment required

45-minute Keynote

16:55-17:40 Room F1+F2+F3 - Plenary

I can’t do this… alone! A Tale of Two Learning Partners

Two-Day Tutorial (12-hour Workshop)

9:00-17:00

Exploring systems quality in a distributed world

Equipment required

If you like the Agile Testing Days Conference you might also like: