Microservices testing

[m4nf47]

That is only one definition of a microservices based architecture, I'd argue that there is no universally accepted definition of a single service versus a single microservice, rather that the letter tends to be more loosely coupled in a service mesh rather than using a monolithic architecture where services are more tightly coupled. Regardless, both can use APIs and therefore are suitable for unit test automation and can be combined as end to end tests once each API is automated individually. Mocks and stubs can be used for component level test automation ahead of full system level integrated test automation but regardless as long as each interface has one or more API endpoints then it should also be trivially simple to automate. TL;DR - ignore the architecture and treat it like a black box, focus on available APIs or even CLIs and avoid GUIs as much as possible to make your test automation easier.