"Introduction to interface testing" punch in to learn day09: Micro service interface: how to use mock to solve chaotic call relationships

For chaotic calling relationships , The train of thought is ： My tested service is service A, Then I don't care about the service B Is it easy to use , As long as the service is guaranteed A Be able to complete the process , You can complete the interface test task . Follow this train of thought , Just use Mock Services disguised as services B And that's it , I don't have to care about service anymore B How many services are called .

How to choose Mock The service framework ？

First , You have to choose based on your own and your team's technology stack

secondly , You want me to write it Mock The service is easy to modify and maintain

If your team has a good technical foundation , Strong development ability , Then I suggest you use the corresponding language Mock frame , for example Java Linguistic Mockito frame （https://github.com/mockito/mockito） and Python Linguistic mock frame （mock · PyPI）.

If your team's technical foundation is relatively weak , Then I recommend you take a look moco, This framework is under development Mock In service , Provides a way that does not require any programming language , You can restrict it by writing it Json Building services , And start the corresponding service through the command , This allows you to quickly develop and start running what you need Mock service .

Mock Service design experience

First , Simplicity is the first element . Regardless of the original service B What a complex business process , You're designing services B Of Mock The service , Just care about service B Can handle several types of parameter combinations , What parameters will be returned by the corresponding service . So you can catch Mock service B The core of design , Can also be completed quickly Mock service B Development of .

secondly , Processing speed is faster than perfect Mock Service is more important . One Mock The service should be able to return parameters correctly and quickly according to the original service , You don't need to waste a lot of time on Mock Service invocation , It's just a means to help you complete interface testing .

Last , Yours Mock The service should be able to start with light weight , And easy to destroy . You should always pay attention to ,Mock Service is just a supplementary service , therefore , No team wants to start a Mock The service needs to wait 5 minute , Or need 100M Of memory . It needs to start quickly 、 Easy to modify and easy to migrate . since Mock Service positioning is a lightweight auxiliary service , Then it should also be easy to destroy , So that when you finish the test , It can quickly and easily release the resources it occupies .