The art of Microservices teaches us:: High trust, low process, no handoffs leading to culture of freedom and responsibility. It is a way to organize your system that provides both opportunities and difficulties for testing. I recently worked with a company transitioning away from a monolithic architecture, and helped them to re-design their automated testing strategy for the new architecture. Crux is simple patterns combined with automated tools. Self-service cloud makes impossible things instant. In this talk I’d like to share some concrete automated testing techniques that I found useful, including selective deployment, approval testing, and event monitoring. I’ll also relate some challenges we encountered enabling the teams developing the various services be able to test and deploy independently of one another.

The key philosophy behind microservices testing is :: write programs that do one thing and do it well. Key approaches are

· Setup domain and CI/CD

· Integrate testing culture with TDD

· Integrate early

· Use Mocks/Stubs to have early POC

· Focus is on test pyramid

· Ensure to visualize and categorize the test coverage for better result.


Outline/Structure of the Case Study

- Introduction to Cloud and DevOps

- Why Microservices

- Compare traditional testing to Cloud testing

- Challenges with Microservices

- Best Practices

- Shared results with experience report

Learning Outcome

Insight into different levels of Mciroservices testing and how to optimise it

Target Audience

Leaders, Agile team members

Prerequisites for Attendees

DevOps, Microservices

schedule Submitted 2 years ago

Public Feedback