Two days ago, Mr. Su San, a teacher of Songqin Software Testing, conducted a bank project interface test training camp, and today I will share the notes of the VIP internal course with you!
1. Interface testing process
01. Interface test plan
Develop: People, Tools/Platforms, Scripts, Time, Standards, Output Interface Test Plan Documentation
02. Bank interface document analysis
(1). Interface name: Describe the function of the interface, no need to test
(2). Interface address: http starts, the same as URL, no need to test
(3). Request method: post/get/delete/put, when an interface has multiple ways, it needs to be tested
(4). Request parameters: field name, field value, constraints, main test object of interface test
(5). Response parameters: no need to test, but the basis for judging whether it is a defect, generally provide the response content of normal data
(6). Error reference code: for example, retcode:0 means normal retcode:1: means wrong username or password
(7).http响应码:200,403,500...
(8). Request header: describes the format of the request parameters, no need to test. Unless the parameter comes from another request
03. Interface use case design
(1). When there are many request parameters, and there are optional and required
A. Divide the parameters into optional and mandatory
B. Detailed testing for required items, and detailed testing is required if optional items involve sensitive information or display impact
(2). Interface use case design method:
The main value used: the boundary value of the equivalence class, if there is a relationship between the fields: the decision table
(3). Output and maintenance of use cases
Platform: testlink, Zen Tao....
Tool: Excel
04. Execution of interface test
(1). When there is an exception in the interface:
First of all, you need to troubleshoot the following problems: interface documentation problems, operation problems
Only then can you confirm that it is a problem with the interface itself
(2). When there is a problem, you can communicate with the developer first
(3). Even if the developer immediately modifies the bug, it is recommended to submit the bug to the platform
(4). Output interface test report
05. Interface test report
Reference template (you can get it directly from the editor!)
2. Practical design of bank interface use cases
Skill requirements: Analyze interface documents, extract test points, analyze business logic, extract the relationship between interfaces or fields, and help interface test case design
3. Introduction and initial use of Postman tools
01. Download and install
Installation: Directly installed on the C drive.If there is a problem, after uninstalling, enter the C disk to search for postman keywords, delete all files with postman, and reinstall it
02. Introduction to the layout of the interface
03. Different request formats in the body are different
The relevant recorded videos of this training camp have been uploaded, and those who need videos can also find the editor to get them!