Tips and tricks on implementing a successful test automation architecture in a Microservices environment.

1. TEST AUTOMATION
ARCHITECTURE IN
MICROSERVICES
Alper Mermer
1

2. TESTING RELATED ISSUES IN MICROSERVICES
Services are built and deployed independently
Services talk to each other to accomplish things
Builds and deploys are automated
Data is not centralized
Cross functionals need to be tested way before the end
Tests need to be executed way earlier
Tests need to be executed way later
2

3. THE INFAMOUS TEST AUTOMATION PYRAMIDE
3

4. INTERNAL TESTS
4

5. EXTERNAL TESTS
5

6. SERVICES ARE BUILT AND DEPLOYED INDEPENDENTLY
6You can’t depend on other services to be up

7. SERVICES ARE BUILT AND DEPLOYED INDEPENDENTLY
7
Use test doubles to resolve your dependencies
Mountebank

8. SERVICES ARE BUILT AND DEPLOYED INDEPENDENTLY
8
Your tests should be able to run in isolation
Docker

9. SERVICES TALK TO EACH OTHER TO ACCOMPLISH THINGS
9Keep the communication between your services alive

10. SERVICES TALK TO EACH OTHER TO ACCOMPLISH THINGS
10
Create Consumer Driven Contract Tests between services
Pact

11. BUILDS AND DEPLOYS ARE AUTOMATED
11You don’t have a buffer time between builds

12. BUILDS AND DEPLOYS ARE AUTOMATED
12
Multiple layers of testing
Layered path to
production deployment
Blue - Green deployments
Canary releases

13. BUILDS AND DEPLOYS ARE AUTOMATED
13
Repeatable environments
Vagrant, Puppet, Chef, Ansible, Docker

14. DATA IS NOT CENTRALIZED
14
You have to manage each test data seperately
Each test creates its own data

15. DATA IS NOT CENTRALIZED
15
Each test data should be unique accross the test suite
Each test deletes only the data it created

16. CROSS FUNCTIONALS NEED TO BE TESTED WAY BEFORE THE
END
16
Again, you can’t wait until everything is completed

17. CROSS FUNCTIONALS NEED TO BE TESTED WAY BEFORE THE
END
17
Put in automated performance tests in your CDP
Jmeter, Gattling, Locust

18. CROSS FUNCTIONALS NEED TO BE TESTED WAY BEFORE THE
END
18
Put in automated security checks in your CDP
OWASP ZAP, OWASP Dependency Check, W3af

19. TESTS NEED TO BE EXECUTED WAY EARLIER
19
Tests aren’t the responsibility of the testers alone
You need to start testing right away

20. TESTS NEED TO BE EXECUTED WAY EARLIER
20
You should minimize testing things as a whole
End to End (E2E) tests

21. TESTS NEED TO BE EXECUTED WAY EARLIER
21
Implement Journey Tests
Selenium, Capybara, Sahi, Appium

22. TESTS NEED TO BE EXECUTED WAY LATER
22
See what’s going on in production
Monitor things

23. TESTS NEED TO BE EXECUTED WAY LATER
23
Analyze trends and problems on production
Have some tests which are run in production

24. TESTS NEED TO BE EXECUTED WAY LATER
24
Be a Quality Analyst

25. COMMON PITFALLS
Don’t use a fixed recipe
Build your architecture
incrementally
Keep your architecture alive
25

26. BOOK SUGGESTIONS
Building Microservices - Designing Fine-Grained Systems, Sam Newman
Infrastructure as Code - Managing Servers in the Cloud, Kief Morris
26

27. 27
THANK YOU
Questions ?
amermer@thoughtworks.com
@alpermermer
@test_hive