Testing
On testing microservices and how we do it.
From Clemson “Testing Strategies in a Microservice Architecture” we have borrowed the following strategies:
- unit
- integration
- component
- contract
- end-to-end
From Clemson “Testing Strategies in a Microservice Architecture” we have borrowed the following strategies:
- unit (solitary + sociable) automated, included in coverage
- integration (testing adapters, classes that communicates with the outside world) automated, included in coverage
- contract (based on specification, “service test”, the artifact that will be deployed) automated
- end-to-end (minimal) mostly manual
next step
As an alternative to end-to-end tests we prefer a technique called semantic monitoring, where we use fake events (synthetic transactions) to ensure that the system is behaving semantically.
Another aspect of testing is timing, when to run what tests:
