Testing Microservices – what do you want to know?

The following is an outline of blog post on Testing Microservices. Does it sound interesting? Vote below to get me to write it or focus on something else :)

Testing Microservices

1) Microservices is a concept a set of patterns, not a set architecture
2) The context in which you testing has a direct impact on how you test
3) Risk changes, allow your strategy to change with it
4) Diversify your testing strategy

If you have a question you want me to answer on testing microservices, please add it in the comments.

2 Comments

  1. Hi Anne-Marie,

    I’ve had a burning question ever since I heard of the concept of microservices – what is generally the most effective strategy for testing microservices within an agile environment?
    I’ve always felt that testing provides the biggest value in an agile environment when it is performed in collaboration with developers and product owners. However, with microservices this tends towards focusing on the individual microservices which can lead to a lack of full system testing.
    My initial thought is to have dedicated testers responsible for testing the full system, considering the integration of each service as a full system as well as dedicated testers responsible for thoroughly testing individual microservices or integrations in greater depth.

    But with limited resources, this solution may not make sense. Is it fair to say that dedicated testers may be better used testing the full system and depending on more development resource to test individual microservices in depth? No matter what the situation, both levels of testing are needed, but are testers skills best focused on the broader picture that so often gets forgotten?

    I look forward to your post!
    Matthew

    Reply

    1. Hi Matthew, my experience has been that both are required but not necessarily at the same time. If I had to chose, I think I would focus on the system rather than the sum of the parts. There’s challenges to this which I will touch on in the blog post, which it seems I now have to write since 9 out of 10 testers think it would be a good idea :)

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>