"Introduction to interface testing" punch in to learn day07: websocket interface: how to test a completely unfamiliar protocol interface?

If you come across a new agreement , You know how to start from scratch , Complete the interface test ？

As a test engineer , We don't need to understand the underlying principles of the Protocol , Just understand how the new protocol transmits data , How to return to the database . in other words , We want to simulate a client to verify the logic of the server , The quickest way to start interface testing is not to look at the protocol documentation , Instead, go directly to the development and implementation of the client code , This is for us , It can solve the problem more directly .

In the face of a strange new agreement ,

1、 The first task of the test engineer ： Is to test the correct logic of the interface 、 Whether the wrong logic meets the initial requirements , therefore , We need to quickly master the means of verification .

therefore , We should start from the perspective of solving practical problems , Directly get the calling client code provided by the development engineer , So we can finish the work quickly ; In the subsequent time of completing the work , We can also slowly add basic knowledge . What you need to pay attention to here is , I'm not saying that basic knowledge is not important , But in the process of the project , Learning basic knowledge is often not important to complete the quality assurance of the project .

2、 Use some familiar tools to complete this test

3、 Use the existing tool base to solve WebSocket After the idea of interface testing was broken , I began to seek to write code , solve WebSocket The interface test . ad locum , I still suggest you start with your own technology stack , Find a way to solve the problem .

4、 take WebSocket Interface encapsulated into your framework

From the modified code , Do you feel the charm of the framework better ？ It can make the code more concise and readable , take WebSocket The protocol is encapsulated into your framework , You have one that includes HTTP The agreement also includes WebSocket The interface testing framework of the Protocol , As you accumulate new agreements , Your framework will become more and more powerful , Your own secret Arsenal will continue to expand , As you improve it , It will make your interface testing easier , Faster and faster .

Summarize ideas ：

The first interface test for a strange protocol , You need to keep your sense of smell sharp , According to their own technical foundation , Solve the problem as soon as possible . Generally speaking , You can quickly complete the test task in three steps ：

1、 Leverage development engineers . The first thing you should borrow is a development engineer , But you don't want to get into the kind of... That development engineers give you , Start with technical basis and theory , Then gradually apply the learning context . You want a fatal blow , Just bring his client code , Use it for your own use as much as possible , Turn it into your own interface test code .

2、 Stand on your own technology stack , Complete technology accumulation . If the development engineer's code can't be used , Then you need to stand on your own technology stack and find a solution , This includes both the testing tools you are already familiar with 、 Test platform , It also includes its own testing framework and coding basis .

3、 Fall into the frame . No matter which method you use , After completing the test , You still need to master the corresponding theoretical basis , At the same time, find a way to make this strange interface , Merge into your own framework in a familiar way , Continuously expand the testing ability of their own framework , Constantly enrich your own testing methods .