Personal thoughts on the development of game automation protocol testing tool

Catalog

Preface

Generalization

One 、 scene

Two 、 Directory structure

3、 ... and 、 catalogue

Four 、 The function interface CASE Operation process ​

  5、 ... and 、 Data structure

1、 Card drawing scene ​

2、 Team mate / robot ( When you are too lazy to open multiple real machine clients , Or there is no real machine on hand )​

6、 ... and 、 Use case recording

---

Preface

From zero to 1 Try to get a tool , The first step from the beginning , Understand packets , After the first agreement is successfully sent in the packet , Think about how to put the documents ,（ Among them, the file name has been thought for a long time , Probably because experience is not enough ） How to organize test results , Up to now, the final finished product , It can be used , But I always feel like something .
When writing this article, I struggled for a long time to express clearly , Because the code cannot be made public , I originally wanted to write a use case , This may be more obvious , But finally give up ...

Generalization

be based on pytest Organize use cases , Run and aggregate reports
Use producer consumer design pattern for protocol sending and receiving
gitlab CI Realize automatic timing trigger

Using language ：python3.7+
frame ：pytest

One 、 scene

1、 Automatic test of functional interface
2、 Batch 、 Repeatability test data construction

Two 、 Directory structure

|_agent
|_case
--|_XX function
----|_get_xxdata.py
----|_xx_test.py
----|_conftest.py
--|_XX function
|_conftest.py
|_command-protocol
|_common
|_dist
|_docs
|_gameconfigs
|_gametools
|_pb2
|_report
|_utils
pytest.ini
run.py
setting.yaml

3、 ... and 、 catalogue

agent: Front and back interaction layer , When writing a new agreement , First write the protocol request method here
case: Use case storage directory , Create a new folder for each function , among conftest.py Perform pre-processing and post-processing before use cases , No need to import , Just pass in the firmware name in the use case function
command-protocol: proto file  
common: Protocol tool file
dist: Store packaged test data tool files
example: Sample file , Some unfamiliar function usage examples
gameconfig: Game item configuration , Mainly planning and configuration
gametools: Test data construction file
docs: Project documentation related
pb2: Protobuff Converted pb file
report: Run report directory （ Do not upload to the remote , Generated locally after running ）
utils： Some auxiliary scripts , For example, lead pb, Generate result code file
pytest.ini： pytest Run setup file
requirements.txt： Third party package import file
run.py: Run case entry file

Four 、 The function interface CASE Operation process

  5、 ... and 、 Data structure

1、 Card drawing scene

2、 Team mate / robot
( When you are too lazy to open multiple real machine clients , Or there is no real machine on hand )

6、 ... and 、 Use case recording

A non game embedded approach , Tell me your thoughts roughly
use Wireshark Capture network packets , preservation Wireshark file , hold Wireshark The file is parsed into json file , The protocol tool then reads json file , Parse into use case steps .

Last ：
The article may not be clear , If you are interested or have any suggestions, you can leave a message