- This topic has 4 replies, 5 voices, and was last updated 3 years, 3 months ago by .
- You must be logged in to reply to this topic.
Has anyone here ever tested Microservices? It is something that I am curious about. Microservices have been called a silver bullet for all architectural problems but I am not too sure about that.
Microservices require a different test strategy too so I am wondering if you have testing microservices, how have you gone about it?
I have tested Microservices. Testing the services themselves is not very hard since they are usually fairly minimalistic in features.
The interesting things to test are all the business rules, transformations, API’s, and data storage.
So when I test microservices I tend to spend a lot of time on the business rules and data transformations, some time at the API and database and fairly little time at the services themselves.
Thanks Kasper. I have just started testing Microservices and I am finding your approach helpful.
Also found this article 3 Tools for Testing Microservices quite relevant to this topic.
2 very simple things to start with:
1. Ensure that you’re using CDC’s(consumer driven contract) type tests to ensure that your micro-services fulfil their contracts with one another.
2. Build out API level tests including synthetics which alert in production when there’s an issue.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.