Amit Rawat discusses the challenges and advantages of testing microservices in cloud environments, contrasting them with monolithic architectures. He emphasizes the benefits of microservices, such as independence, flexibility, and ease of deployment, while cautioning against anti-patterns that may lead to complications. The document also highlights various testing strategies including contract testing, non-functional testing, and the importance of resilience and fault-tolerance.

1. Testing of Microservices in a Cloud Environment
Amit Rawat

2. Hello!
I am Amit Rawat
I am here because I love to talk on Test
Automation.
“I am a Civil Engineer by qualification, a Test
Automation Architect by profession and a
Developer by passion.”
You can find me at:
Twitter/Medium: @sahajamit
Email: sahajamit@gmail.com

3. My BLog: http://www.amitrawat.tech/

4. Testing
of
Services(Micro)Services

5. Monolithic Applications

6. Positives of Monolithic Architecture
Image Source: https://dzone.com/articles/microservices-1-introduction-monolithic-vs-microse

7. Drawbacks of Monolithic Architecture
- has limitation in size and complexity
- too large and complex to fully understand and made changes
fast and correctly
- Re-deploy the entire application on each update.
- Impact of a change is not easily traceable and it leads to
extensive manual testing
- Single point of failure.
- Not flexible to adopt new technologies/languages

8. Microservices
Microservices Google Trends Growth Over 5 years

9. Microservices
Image Source: https://dzone.com/articles/microservices-1-introduction-monolithic-vs-microse

10. Microservices at-scale

11. Microservices at-scale
500+ services 500+ services

12. Why Microservices?
Image Source: https://dzone.com/articles/microservices-1-introduction-monolithic-vs-microse
● Services are small, independent and loosely coupled
● Each service is a separate code base managed by a small dev team
● Services can be deployed to production independently
● Services communicate to each other using a well defined api
(contract/schemas)
● Services do not need to share the same tech stack, libraries or
frameworks
● Responsible for persisting their own data

13. Microservices Anti-patterns

14. Microservices Anti-patterns
● Breaking the monolith in to pieces without intentional
division of services either by domain or unit of work
you end up creating several mini monoliths.
● Everything micro except data
● Relying on consumer sign-offs
● Building a gateway in every service

15. Testing the entire stack of Microservices
Source: https://twitter.com/simform/status/1133352132013199366

16. Testing Pyramid

17. Infamous Testing Pyramid
Source: https://www.slideshare.net/AlperMermer/test-automation-architecture-in-microservices

18. Test Automation Pentagon
A B C
D E F

19. Component Tests
Source: https://alexromanov.github.io/2019/04/02/spring-boot-docker-containers/

20. Contract Testing

21. What is a contract?

22. Source: https://www.atlassian.com/blog/technology/spec-first-api-development
User Service
Billing
Service

23. Breach of Contract

24. Source: https://www.atlassian.com/blog/technology/spec-first-api-development
User Service
Billing
Service

25. PACT to the rescue

26. Consumer side verification
CONSUMER
Billing
Service
PROVIDER
User
Service
Request
Response
Pact Mocked Provider

27. Producer side verification
CONSUMER
Billing
Service
PROVIDER
User
Service
Request
Response
Pact Mocked Consumer

28. Contract Testing: Take 2
Source: https://docs.confluent.io/current/schema-registry/index.html

29. End-to-end Journey tests
● Try to have as few end-to-end tests as possible.
● Focus on important user journeys
● Use Infrastructure as a code for repeatability
● Make your tests data-independent
Source: https://www.hanoverresearch.com/insights-blog/4-tests-measure-customer-journey-mapping/

30. Non-Functional Testing in Microservices
● Resilience / Fault-tolerance Testing
● Chaos Testing
● Config and Service Discovery testing
● Elasticity Testing

31. Resilience Testing
● Fallbacks
● Retries
● Timeouts
● Circuit breakers

32. Chaos
Testing/Experiments

33. Monkey Testing

34. Monkey creating chaos in cloud
● Adding latencies
● Microservice/s failure
● Node failure
● Region Failure
● Cascading failures

35. Not If this fails,
but when it fails
Cultural Shift

36. Config Testing

37. Elasticity or Auto-scalability testing

38. Let’s Conclude
Source: https://medium.com/@copyconstruct/testing-microservices-the-sane-way-9bb31d158c16
Shift Left Shift Right