Automation Testing in Microservices
A compilation of the different kinds of automation testing in microservices.
Join the DZone community and get the full member experience.Join For Free
Automation tests are a very important requirement to have highly successful microservice architectures. In order to take things to live on a frequent basis, it is imperative to have great automation tests. In this article, we talk about the five kinds of automation tests that you can write, for your microservices.
You may also like: What is API Testing, and Are You Doing It Right?
When you develop an application, it could contain a large number of classes, each of which probably has several methods. You normally write a test case for a particular unit of code. A unit could be a method, a group of methods, or the entire code of a class. Typically, you want to keep the individual unit tests as independent as possible.
A common approach to unit testing is to mock external dependencies, for effectively testing the business logic. For example, a unit test could be run independently of a database. This ensures that tests do not have external dependencies and do not fail when something external to the test changes.
Layer Integration Tests
When we develop enterprise applications, we generally structure them into layers. For instance, a web application could have web, business and data layers. You would want these separate layers to work well together. Therefore, you write layer integration tests to ensure their proper integration.
For example, when you make a call to the web layer, is it being propagated correctly to the business layer, and from there to the data layer? Finally, are you getting a proper response to the request?
When we create a microservice, we end up offering APIs for consumers to access and consume resources. Examples are REST and SOAP APIs. You can test an API by writing an automation test for it. Even for such API tests, the need of the hour is an in-memory database, as it is good to avoid external dependencies.
Here is where all the systems external to our application come into the picture, during testing. You would start accounting for databases, external interfaces and other dependencies needed by your application. This is where you actually deploy your application in a real-world environment.
User Acceptance Tests
This is the final level of automation testing, where you test every aspect of the end-user usage scenarios. The focus here is on creating real-time usage scenarios, such as accessing a production-mode database for testing the logic. This step is necessary before you make the application live.
In this article, we explored the five different kinds of automation testing that are generally performed on applications. These are unit testing, layer integration testing, API testing, system testing, and user acceptance testing.
Published at DZone with permission of Nilabh Mishra. See the original article here.
Opinions expressed by DZone contributors are their own.