Humans in Microservices Automation Testing – best practices from a human developer to a human tester –

Year 2011 was the first time somebody saw an initial form of it, 2012 they give it a name: Microservice, then the world started to follow Martin Fowler on how he describes Microservices Oriented Architecture.
People were meeting secretly to discuss about them, then the innovators started to give talks at conferences about them, and everybody was debating but nobody was actually doing it, adopting in complex systems microservices implementations.
These days other buzz words are in trend, so we are not talking about them anymore, we are using them, almost everywhere; even banks, who are very resilient to change are re-writing their solutions using microservices architecture.Nowadays we are using them that much that people started to find reasons for why they are not so good.

That’s true!
Microservices oriented architecture is not the silver lining, and most of the time, is the decisions of the whole team on the best approach to use, there is so much flexibility in how to build a whole complex system out of pieces in such architectures, that the only thing we do always and we do it good, is writing automated testing for each individual microservice and for the integration of the whole system.

I had the opportunity to use them for start-ups building IoT and Smart Office solutions, i used them for large e-government solutions or even for innovative paperless banking product, and everytime i had to make sure things are working just fine before we can call ourselves production ready.

Let’s have a trial and error workshop together, let’s combine knowledge and best practices from both tester and developer side, to be able to build better automation testing for microservices oriented systems.
I will put on the table my experience in writing microservices solutions, building distributed architectures, writing unit and load tests for them and working closely to QA team, you will bring your A-game on how to design complex test strategy and we will achieve together some interesting stuff.

Topics covered

  • sync vs async communication
  • write API test for single microservices;
  • how to design and re-use code between several microservices tests
  • apply DTO patterns
  • translating user journeys into actionable tests
  • translating microservice related risks into actionable tests


No worries, pair programming will be involved, I will help along with your assignments, there will be also demo with my existing solutions, debates is not gonna miss either as we value everybody’s opinions or suggestions, and of course we gonna choose and solve together the challenges whole day long.
See you soon!

Key Takeaways

  • understanding the underlying concepts of microservices architecture
  • designing highly maintainable testing framework
  • identifying user journeys and translating them into reliable/manageable tests
  • managing test data


  • Java version JDK 8 or above
  • Docker 2.2 or latest
  • IDE: IntelliJ IDEA or similar
  • Dependency Management: Maven
  • Admin rights on laptop or similar to be able to install and run all of the above
4hWorkshop Automation