Testing in micro-services

Each person's development ability is different, must ensure the online application is not the problem, the interface availability rate reaches 100%, no skylight, no bug

Difficulty or relatively large, especially the business development of a lot to be with the version of hair, time tight, task heavy problem more serious.

Strengthen the demand rationality review, design rationality review, code review.

Unit test: (JUnit) Try to overwrite the path as much as possible. (Disadvantage code implementation is unreasonable, code structure modification, the entire

Changes in program structure can result in a large amount of test case modifications).
Integration testing: (self-developed) automated read configuration of multiple types of pins, universal calling interface, matching results returned

Number, return type, partial pin match to return value. Self-developed integration testing tools to achieve several, hundreds of, thousands,

Tens of thousands of pin test 100% availability, skylight can be achieved.

　　Micro-service integration test design principle, through generalization call, generalization call interface implementation, editable multi-set input parameter configuration,

And the number of returned results, the return value type control and the correct type, and matching validation.

　　

　　

Testing in micro-services