I’m Huang Caicai, and I am inspired to become the most potent boy in boxing session. I chatted with Hapi group friends for a day and found that many group friends don’t know how to do interface testing software testing, so I roughly wrote this article. I hope to be helpful.
If you want to discuss with my hapi group friends how to learn python automated software testing, you can click here ✔←
1. What is an interface
Software interface
2. Process interface testing is a special item
Demand -> Planning -> Use Case Design -> Implementation -> Report
Interface Document -> Use Case Design -> Execution Use Case (bug) -> Special Report
Without interface documentation, how to do interface testing? Fiddler
Three: interface document
Interface name: Indicate the function of the
interface. Interface address: URL HTTP/HTTPS
Request method: post/get
Request parameters: Required items, optional items The test
explains the corresponding situation of the optional parameters, then also design use cases to cover
gender: male /女苏三
Return format: xml/json
Return parameters: expected result, comparison
Four. Test cases
Cover all parameters, forward use case
Cover all required parameters, forward use case
A certain required parameter is empty, reverse use case empty=space? The position of the space: front, back, middle, null
based on required parameters, pass one less parameter,
multiple parameters passed a reverse use cases (discussed below)
required parameter wrong data type, the data value of the error, the reverse use cases (e.g. integer variable string)
any combination of optional parameters, with positive cases
and associated business logic, user identity The authentication is empty or wrong, reverse use case
field uniqueness check, such as inserting data field cannot be repeated, send two requests, check the second return result
How is the function implemented? The 11-digit mobile phone number ID number cannot be repeated —> Send the request repeatedly
Five. Interface test
postman Jmeter guide and let him know what you are good at
Error reference code: Do you need to design use cases for coverage?
When there is a bug:-effective communication,
first confirm with the development
Six. Classic bug
-
The parameter is null or empty string "" etc.
-
Permission is not processed, you can access other users' information
For example: access without permission, or general users can access administrator permissions)
-
Improper state handling, leading to logic errors (maybe programmers 123 are confused)
-
Potential performance problems (submitting in the background or raising performance risks in advance)
5. The logical verification is not perfect, and the loopholes can be used to obtain illegitimate benefits, etc.
7. What exactly is an interface?
The external interface of the system? The internal interface of the program
What are the composition of the interface ? The
significance of
interface testing Common requests for interface testing? Post a get difference
What should I pay attention to when designing interface test cases?
Interface testing process
Interface response status code: http response code
http/https protocol
Conclusion
That’s all. I recently compiled a collection of interview questions about software testing, as well as some classic resume templates, which are free for everyone. If you need it, you can click here to join the group chat and get it for free
Follow, don’t get lost, if it helps, remember to like and support!