This document discusses strategies for testing microservice architectures. It describes some issues with monolithic architectures like scalability and technology commitment. Microservices offer benefits like independent development and scalability. The document then discusses different levels of testing for microservices, including unit, integration, contract, and end-to-end tests. It notes challenges with end-to-end testing like external dependencies. Various tools and approaches are presented for different types of microservices testing.

1. TESTING
MICROSERVICE
ARCHITECTURE
ŁUKASZ ROSŁONEK

2. ŁUKASZ ROSŁONEK
# Senior Test Engineer
# TestDetective.com

3. MONOLITH ARCHITECTURE
ISSUES:
# application scalability
# technology stack commitment
# reversed learning curve
# development process
# single point of failure

4. MICROSERVICE ARCHITECTURE
PROS:
# independent development
# continuous deployment
# scalability
# technology diversity
# fault isolation

5. WHAT’S THE RUSH ?

6. HTTP REQUEST -> RESPONSE
client
db
ValidationService/NewUser

7. REST / JSON API
PUT/NewUser
{
name: “John”,
surname: “Snow”,
address: {
city: “Winterfell”,
land: “Seven Kingdoms”
}
}
UserService:
201 Created
{
UserId: “1”
}

8. WEBSERVICE ANATOMY
ORM
API
DOMAIN
SERVICE
EXTERNAL
CLIENTS
DB

9. TESTING STRATEGIES
# unit tests
# integration tests
# contract tests
# end-to-end tests

10. UNIT TESTING
ORM
API
DOMAIN
SERVICE
EXTERNAL
CLIENTS

11. WHAT’S THE PROBLEM ?

12. INTEGRATION TESTING
ORM
API
DOMAIN
SERVICE
EXTERNAL
CLIENTS
DB

13. WHAT’S THE PROBLEM ?

14. CONTRACT TESTING

15. END-TO-END TESTS

16. END-2-END TESTING
CHALLENGES
# test releases stability
# network calls issues
# external services debugging

17. END-2-END TESTS PATTERNS
# as few as possible
# focus on user perspective
# user perspective != GUI
# test environment as code

18. TOOLBOX

19. WHY MOCKS ?

20. WIREMOCK

21. WHY TEST CONTRACTS ?

22. CDT TESTING - ACCUREST
Validation
Service
/NewUser
producing stubs
API
stubs
run test
against

23. WHY E2E TESTS ?

24. E2E TEST – REST ASSURED
public void getUserData(String userId) {
given().
contentType("application/json").
when().
get("/user/" + userId).
then().
body(containsString("id")).
statusCode(200);
}
@Test
public void shouldRetrieveUserData() {
RestService service = new RestService();
service.getUserData("1");
}

25. Q&A?
# lukasz.roslonek@gmail.com
# twitter.com/TestDetective
# www.testdetective.com