Testing Microservices Architecture

TESTING
MICROSERVICE
ARCHITECTURE
ŁUKASZ ROSŁONEK

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

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

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

HTTP REQUEST -> RESPONSE
client
db
ValidationService/NewUser

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

WEBSERVICE ANATOMY
ORM
API
DOMAIN
SERVICE
EXTERNAL
CLIENTS
DB

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

UNIT TESTING
ORM
API
DOMAIN
SERVICE
EXTERNAL
CLIENTS

INTEGRATION TESTING
ORM
API
DOMAIN
SERVICE
EXTERNAL
CLIENTS
DB

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

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

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

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");
}

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

Testing Microservices Architecture

More Related Content

What's hot (20)

Similar to Testing Microservices Architecture (20)

Recently uploaded (20)

Testing Microservices Architecture

Editor's Notes