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?
1 Like
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? 
1 Like
Hello! You can check my compilation of resources on testing microservices: here
3 Likes
@vin I found this post on the topic of microservices, you might find it useful:
2 Likes
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.
2 Likes
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.
2 Likes