Testing
Testing is a fundamental aspect of any software development. No matter how good the development team is, there is always scope for improvement or something has been left out of their training. Testing is usually a time-consuming activity that does not get the required attention at all. This has led to the prevalence of behavior-driven development, where developers write unit test cases, then write code, and then run a coverage report to know the status of the test cases.
What and how to test
As microservices are totally distributed, the main question that comes to mind is what to test and how to test. First, let's have a quick look at the major characteristics that define microservices and need to be tested:
- Independent deployment: Whenever any
- small or a safe change has been deployed to a microservice, the microservice is ready to be deployed to production. But how do we know whether the change is safe or not? This is where automation test cases and code coverage come into the picture...