Looking back on the onboarding test that has been going on for 10 years, I didn’t know much about interface testing when I first entered the workplace. Later, due to business needs, I gradually started to get involved in interface testing. From the initial use of tools for interface testing to writing code to implement interface automation, to the final test platform development. Looking back on this journey, I have deep feelings. Therefore, in order to avoid students who plan to learn interface testing from taking the wrong path, I would like to share my learning experience. I have shared interfaces on Zhihu several times before.
1. The importance of interfaces
In the current software testing industry, interface testing is basically a necessary skill for software testing engineers. If we browse any large company, we will have clear requirements for interface testing. Moreover, for a student who is new to software testing, interface testing is more important than itself! ! ! Why do you say that? Nowadays, when laymen hear about software testing, what they think of is "bits and pieces" of manual testing. But the real software testing experts, we call it "test development". The biggest difference between manual testing and test development is automation. If you plan to move from manual testing to test development, interfaces and interface testing are the only intermediate media.
Software test engineer promotion path
2. The role of interfaces in software
All the functions we see in the UI interface of the software are implemented through interfaces. For example, in the login interface, the username and password you enter on the login page are passed to the back-end server through the login interface, and then the back-end server returns the login result (login successful/login failed) to the front-end UI interface through the interface. When we test the login function, what we actually test is whether the function of the login interface has been implemented by back-end development. Therefore, interface testing will be closer to the code developed and written, and it will be easier to implement automated testing.
3. Learning experience/video sharing
The learning of any knowledge cannot be achieved overnight, but is a gradual process. So I divide the learning of interface testing into three stages: Stage 1: Basic stage
1. Understand the concepts related to interfaces and interface testing
2. Master the method of writing high-quality interface test cases
3. Master the use of tools to complete interface testing and interface automation testing
4. Understand the concepts related to performance testing
5. Use tools to complete interface performance testing
In the first stage, learning is not very difficult, mainly the understanding of concepts and the use of tools. If you are in the workplace, it is easy to turn this theoretical knowledge into practical applications. If you have not entered the software testing industry and understand this knowledge, I suggest you stop learning first and find a job related to software testing. Because it is empty talk and not combined with reality, it is difficult to truly understand the application significance of interfaces and performance in software testing. And in the current market, in Beijing, Shanghai, Guangzhou and Shenzhen, for software engineers who can complete interface + performance testing, the offers are basically around 11K. If you are a university undergraduate, 13~15K is possible. Learning resources at this stage are also provided: 1) "Interface test that even a novice can understand in one hour"
现在我也找了很多测试的朋友，做了一个分享技术的交流群，共享了很多我们收集的技术文档和视频教程。
如果你不想再体验自学时找不到资源，没人解答问题，坚持几天便放弃的感受
可以加入我们一起交流。而且还有很多在自动化，性能，安全，测试开发等等方面有一定建树的技术大牛
分享他们的经验，还会分享很多直播讲座和技术沙龙
可以免费学习！划重点！开源的！！！
qq群号：110685036
1. Able to use code to complete interface testing
2. Able to build an interface automation framework and implement interface test cases
This stage is mainly about the use of code. For an ambitious and aspiring software testing engineer, coding is definitely something that must be learned. If you have no coding foundation, python is a good entry point. And in software testing projects, interface automation is the most commonly used.
1. Understand the continuous integration of interface automation
2. Understand the Mock testing of the interface
3. Understand the interface testing methods of other protocols
If you are in the workplace, you don't actually need to spend time studying. You just need to learn about it occasionally in your usual time to expand the breadth of your knowledge.
4. Suggestions on interface tools that need to be learned
Finally, let me talk about the tools you need to learn about interface testing:
1. Must master:
1. Developer tools of fiddler/Charles+chrome: These are packet capture tools. The interfaces of the first two packet capture APPs are very easy to use, and the latter one is very convenient for testing WEB-side projects. Of course, these three tools are not very difficult to learn, and even if you master them all, it won't take much time.
2. postman: Interface debugging tool, the easiest to use and the most convenient interface testing tool. It is strongly recommended that you must be able to use it. Even if you can use code or Jmeter to implement automated interface testing, this tool must be mastered.
3.Jmeter: Another very powerful interface testing tool. It can help us complete interface testing, interface performance testing, and interface automation testing. With such a powerful function, what are you waiting for? It must be learned and mastered. Once we learn to use Jmeter, we will no longer be afraid of interface-related tests.
4.Jenkins: the main tool for continuous integration. If you want to complete automated testing, you must master the use of this tool. The difficulty with this tool is how to build it. But in our projects, Jenkins is usually set up, so we focus on learning how to create Jenkins tasks and automatically execute tasks.
5.git: version control tool. In fact, you can also understand it as uploading/downloading codes or scripts (Jmeter) in automation projects in automation.
2. Understand:
soupUI: Professional soup protocol interface testing tool
telnet command: tool to execute Dubbo protocol
ps: The soup and dubbo protocols are not mainstream interface protocols in the current software development industry. The mainstream interface protocols are still http and https.
Finally, I would like to thank everyone who read my article carefully. Looking at the increase in fans and attention, there is always some courtesy. Although it is not a very valuable thing, if you can use it, you can take it directly!
Software Testing Interview Document
We must study to find a high-paying job. The following interview questions are from the latest interview materials from first-tier Internet companies such as Alibaba, Tencent, Byte, etc., and some Byte bosses have given authoritative answers. After finishing this set I believe everyone can find a satisfactory job based on the interview information.
