This document discusses testing strategies for microservice architectures. It begins with an overview of microservice architecture and its advantages and disadvantages. It then covers the different levels of software testing in the context of microservices, including unit, integration, component, and end-to-end testing. The document also discusses various testing strategies that can be used like documentation-first, full stack in-a-box, shared testing instances, stubbed services, acceptance testing, and contract testing. It emphasizes the importance of test automation and shows the agile testing quadrant for microservices.

1. Testing Strategies in a
Microservice
Architecture:
Independence vs
Integration

2. Hello!
My name is Yana Muntianova
I am QA Engineer at
I am ISTQB ® Certified Tester
(Foundation Level)
2

3. AGENDA:
1. Microservice Architecture.
Pros and Cons.
2. Levels of Software
Testing.
3. Other Testing Strategies.
3

4. Microservice Architecture.
Pros and Cons
Let’s start with a brief overview of microservices
1

5. Microservice
architectural style is
an approach to developing a single
application as a suite of small services,
each running in its own process and
communicating with lightweight
mechanisms, often an HTTP resource API.
5Martin Fowler, James Lewis

6. Companies that use/used microservice architecture 6

7. 7
Monolithic Architecture Microservice architecture
Client
Reverse Proxy
Service
Datastore
Service
Service
Service
Service
DS DS DS DS

8. 8Advantages
Independence Ready-to-market time Scalability Resiliency
Deployment Accessibility Isolation Openness

9. 9Disadvantages
Testing Dependencies Deployment Managing
Versioning Unification Logging Debugging

10. Levels of Software Testing
Let’s take a look at levels in testing microservices context
2

11. Expectations vs. Reality
11
UI
UI cmpnnt
API
Business
logic
DS
UI cmpnnt
API
Business
logic
DS
UI cmpnnt
API
Business
logic
DS
UI
UI cmpnnt
API
Business
logic
DS
UI cmpnnt
API
Business
logic
DS
UI cmpnnt
API
Business
logic
DS

12. Test Levels
12
According to ISTQB In Microservices testing
Unit
Integration
System
Acceptance
Unit
Integration
Component
E2E
Exploratory

13. Unit testing
13
Sociable unit testing
Solitary unit testing

14. Integration testing
14
Service
External
service
External datastore

15. Component testing
15
Service

16. E2E testing
16
Service A Service B
Service C Service D
Service E Service F
IN
OUT

17. Exploratory testing
17

18. One more time
18
Unit
Integration
Component
E2E
Exploratory
time
cost

19. Other Testing Strategies
Let’s go through some helpful approaches
3

20. Strategies:
➢ The documentation-first strategy
➢ The full stack in-a-box strategy
➢ The shared testing instances strategy
➢ The stubbed services strategy
➢ The acceptance strategy
➢ Contract testing strategy
20

21. Test automation?
21Unit
Service:
➢ API
➢ Component
➢ Integration
UI
Contract test

22. Agile Testing Quadrant
22
Functional
Story
Prototypes
Simulations
Performance & Load
Security
Unit
Component
Exploratory
Scenario Based
Usability
Acceptance
Technology Facing
Business Facing
CritiqueProduct
Supportingtheteam
Automated
ManualAutomated &
Manual
Tools
Lisa Crispin, Brian Marick
Q1
Q2 Q3
Q4

23. Useful links:
23
Testing Strategies in a Microservice Architecture
The Practical Test Pyramid
Verifying Microservice Integrations with Contract Testing
End-to-End Automated Testing in a Microservices Architecture
What are microservices really all about?
Microservice Architecture

24. 24
Questions?

25. Thank you for your attention!
25