Now the requirements for testers are getting higher and higher, not only to do a good job in functional testing, but also more and more for interface testing!
Therefore, more and more students are asking, how can we do a good job in interface testing?
To really do a good job in interface testing and understand how to test the interface, you need to analyze the problem from the following aspects, and then find out the direction of learning, so that you can strategize in your work.
1. Tool selection
Tool selection:
◆ J meters
◆ soap
◆ postman
◆ fiddler
◆ Coding
◆ Other tools
Then you can see that we have a variety of tools and solutions for novices to choose from. Since our title is Jmeter, we will focus on how to use Jmeter to test the interface.
Two, the classification of the interface
Classification of interfaces:
◆ http:Jmeter soapui postman
◆ socket:Jmeter
◆ webservice:Jmeter soapui
Before performing an interface test, you must figure out what protocol your interface is, so that you can choose a tool or install a corresponding plug-in for the tool based on this!
For example, if it is a socket protocol and you need to use Jmeter to test, then you must install the plug-in in advance to complete the test smoothly.
If you don't know what the protocol is, you can ask the developers!
3. Jmeter test interface
What knowledge should be mastered in Jmeter test interface?
For this problem, we also need to make a classification description, so as to help everyone sort out.
(Here, as an example, we use the HTTP type interface to illustrate)
A: The necessary knowledge for simple interface testing (does not involve any cookie session or association) is:
◆ How to add a thread group
◆ How to add http sampler
◆ Learn and use the interface function of http sampler
◆ The use and learning of the view result tree component in the listener
It can be said that this is the basic requirement for interface testing, which we call part A.
B: Interface testing involving cookie/session/parameterization/association
The necessary knowledge is part A, and the following points:
◆ http cookie manager
◆ http header manager
◆ Parameterization: csv data set config component uses
◆ Association: regular expression extractor, json expression extractor
It can be said that the above points are necessary for advanced interface testing, which we call part B.
C: Interface testing involving java code (for example, encryption algorithms are required or test results are stored in Excel)
The knowledge that must be mastered is part A+B, and the following points:
◆ Learning and using beanshell sampler components
◆ Basic java coding ability
Basically, if you have mastered the three parts of A/B/C, then you can perfectly do the interface test.
What we are talking about here is what knowledge points or the use of components need to be mastered, and it does not explain how to test. You can also see that according to the different protocols of the interface, the difficulty of the interface is different, and the knowledge we need to master is also different, so we have to do A good interface test still needs to be broken down individually.
Here I recommend a very good video for everyone, from the use of Jmeter's basic components to the actual combat of the HTTP interface, covering three parts of A/B/C, and learning with actual combat drive!
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:
Software testing interview applet
The software test question bank maxed out by millions of people! ! ! Who is who knows! ! ! The most comprehensive quiz mini program on the whole network, you can use your mobile phone to do the quizzes, on the subway or on the bus, roll it up!
The following interview question sections are covered:
1. Basic theory of software testing, 2. web, app, interface function testing, 3. network, 4. database, 5. linux
6. web, app, interface automation, 7. performance testing, 8. programming basics, 9. hr interview questions, 10. open test questions, 11. security testing, 12. computer basics
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. I hope it can help you too!