It is very easy with microservices to create something that nobody can figure out how to start everything needed for a full system test on their development machine. This is one of the downsides of microservices and if you use them you should be mitigating this somehow. (I don't work in a microservices environment and I can think of a dozen options - I'm sure someone who does can think of more as well as tell me why some of my ideas don't work)
Huh, it has lot to do with Micro service. Now we have so many moving parts in form of micro services that dev, qa, UAT testing does not mean much because each team is different timeline for release and final solution will have same version all across is not guaranteed.
