# Best tool for Micro Services

**URL:** <https://club.ministryoftesting.com/t/best-tool-for-micro-services/53465>\
**Category:** Archive\
**Tags:** tools, microservices\
**Created:** [22 September 2021 10:48 UTC](https://club.ministryoftesting.com/t/best-tool-for-micro-services/53465 "2021-09-22T10:48:40Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![vin](https://avatars.discourse-cdn.com/v4/letter/v/a87d85/32.png) [@vin](https://club.ministryoftesting.com/u/vin)\
**Post date:** [22 September 2021 10:48 UTC](https://club.ministryoftesting.com/t/best-tool-for-micro-services/53465/1 "2021-09-22T10:48:40Z")

</div>

In my team the existing application will be re-architected into micro services. What kind of tool would you suggest/ think is beneficial as per your experience/ knowledge? Any guidance on Test Strategy best practices for Microservices?

---

<div class="post-metadata">

**Author:** ![kristof](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/kristof/32/10839_2.png) [@kristof](https://club.ministryoftesting.com/u/kristof)\
**Post date:** [22 September 2021 10:52 UTC](https://club.ministryoftesting.com/t/best-tool-for-micro-services/53465/2 "2021-09-22T10:52:20Z")

</div>

> [@vin](#):
>
> What kind of tool would you suggest/ think is beneficial as per your experience/ knowledge?

The tool that fits your requirements best. I can suggest you that I like Postman or RestSharp but if it doesn’t do what you need or you don’t know JavaScript nor C#. Then it’s rather useless 😛

So what are your needs, can you give us a bit more context? 😉

---

<div class="post-metadata">

**Author:** ![al8xr](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/al8xr/32/14743_2.png) [@al8xr](https://club.ministryoftesting.com/u/al8xr)\
**Post date:** [22 September 2021 11:02 UTC](https://club.ministryoftesting.com/t/best-tool-for-micro-services/53465/3 "2021-09-22T11:02:45Z")

</div>

Hello! You can check my compilation of resources on testing microservices: [here](https://alexromanov.github.io/2021/06/28/microservices-test-resources/)

---

<div class="post-metadata">

**Author:** ![mirza](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/mirza/32/9965_2.png) [@mirza](https://club.ministryoftesting.com/u/mirza)\
**Post date:** [22 September 2021 13:05 UTC](https://club.ministryoftesting.com/t/best-tool-for-micro-services/53465/4 "2021-09-22T13:05:58Z")

</div>

@vin I found this post on the topic of microservices, you might find it useful:

> [@Study project about QA strategy for microservices projects](https://club.ministryoftesting.com/t/study-project-about-qa-strategy-for-microservices-projects/46044/2):
>
> Complementing what I mentioned about the E2E tests above: I tried to list which details could be identified in the E2E test, and not by the other tests, specifically for my context. I took as an example, the functionality to create a purchase order, where the “shop” module will perform a synchronous communication with the “inventory” module and an asynchronous communication with the “shipment” module. Timeout in synchronous communication; Inventory module is not running when creating the orde…

---

<div class="post-metadata">

**Author:** ![ernie](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/ernie/32/2340_2.png) [@ernie](https://club.ministryoftesting.com/u/ernie)\
**Post date:** [23 September 2021 03:45 UTC](https://club.ministryoftesting.com/t/best-tool-for-micro-services/53465/5 "2021-09-23T03:45:33Z")

</div>

Without knowing a lot about the micro-services, it’s really hard to recommend anything. I’d spend more time learning whatever new technologies are involved than any tool. I think most importantly, focus on learning the underlying message layer - Rabbit, Kafka, gRPC, etc, whatever your team is using. This could easily lean to learning Protobuf or other technologies.

I’d also recommend focus on shifting your perspective, thinking about testing micros individually and how that changes the test boundaries, as well as end-to-end testing, and how this is going to fit into your test pyramid.

---

<div class="post-metadata">

**Author:** ![ipstefan](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/ipstefan/32/8279_2.png) [@ipstefan](https://club.ministryoftesting.com/u/ipstefan)\
**Post date:** [27 September 2021 11:53 UTC](https://club.ministryoftesting.com/t/best-tool-for-micro-services/53465/6 "2021-09-27T11:53:44Z")

</div>

Communication and basic learning about the new application needs at business, product, system, project, technical levels.  
I’ve seen too many times projects with microservices being tested for the wrong things…  
The projects were taking double the initial time, due to a disconnect between the above items, which the testers didn’t focus on.  
Get involved and test early: sketches, mockups, business and architecture diagrams, conversations at business/technical levels, whiteboard discussions, etc… try to make sense of things that might derail the product or project.
