foreword
Today we will talk about interface design and use case design. When it comes to this interface, I believe that most testers have encountered some difficult problems, so today we will summarize the difficulties encountered in the interface.
1. Interface use case design
Interface test cases can be designed from three aspects: function, performance, and security.
See the following mind map for details :
2. Summary of frequently asked questions about the interface
interface technical level
1. The verification and verification of input parameters is not comprehensive. like:
- Input parameter data type length boundary, range boundary.
- Input parameter data content, member content, valid and invalid, legal and illegal.
- Input parameter data special character sensitive character filtering.
- Whether the entry is optional or not is mandatory.
2. Service-related logic issues triggered within the interface. like:
- Interface constraints are insufficient. Numerical restrictions, state restrictions, relationship restrictions, authority restrictions, time restrictions, etc.
- The request object and the return object do not conform to the restrictions of business rules, and the length of the return type is unlimited.
- Request time series control limit problem.
- The state of the object under test (request or return) controls the question.
3. The content of the interface return value does not meet the requirements.
- The content of the service definition error code is improper. The scene is improperly handled.
- timeout control logic
4. Interface function security issues.
5. Interface performance problem.
6. The interface request is inconsistent with the wiki document.
7. The interface address change causes unavailability.
interface business layer
1. The content returned by the interface does not meet the business requirements.
- Does not meet the front-end display requirements.
- It does not meet the current front-end business scenarios.
2. The landing data problem involved in the interface.
- The service calculation processing logic causes the data returned by the interface to be incorrect.
- The landing data caused by the triggered service calculation logic is incorrect.
3. Interface compatibility and lack of scalability.
Finally, I would like to thank everyone who has read my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it:
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey, and I hope it can help you! Partners can click the small card below to receive