Introduction to the

“To do good work must first sharpen its tools”, through the introduction of the previous few articles, we roughly have a further understanding of the interface. So let’s look at the tools available for interface testing. Today, there are many tools on the market that support interface testing. Using tools for interface testing can provide testing efficiency. For example, false

Let you complete 100 interface test tasks a day, you think you can work overtime to complete, then 1000, 10000…….. . If you have tools, you can greatly increase your productivity and achieve more with less effort, but not all tools can support you to accomplish this task. Here’s a look at some of the most common and common tools,

Just a quick introduction. If you need or are interested in the online view of the corresponding information of various tools for in-depth learning, here to lead you to understand, encounter these tools will use, understand, know these tools will achieve the purpose, do not talk about the test tools, ask three do not know, a face meng force, that is embarrassing

.

Interface test tool

The interface test tool is shown as follows:

1.Fiddler

First, this is an HTTP protocol debugging proxy tool, which is basically a tool to capture HTTP packets. Both Web testing and mobile testing can use this tool. Since it is HTTP, the tool also supports interface testing. Later in this article, I’ll focus on fiddler. Fiddler: Portal

2.PostMan

Postman is a very popular API debugging tool. In fact, developers use it more. Because testers have more options for interface testing, such as Jmeter, soapUI, and so on. However, Postman is simple enough and powerful enough to debug interfaces during development. This is a Google app

The programmer developed a plug-in, can be installed on the Chrome browser. Supports different interface test requests, manages test suites and automates operations, but the weakness is that automated assertions are not powerful. Continuous integration testing cannot be performed with Jenkins and the code management library. However, it is definitely a good semi-manual, semi-automated test

Test tools, I generally write automatic interface test cases, will open Postman for auxiliary testing and debug. This tool will also be introduced later in the article. PostMan tool introduction: portal

Postman Video tutorials:

Link: pan.baidu.com/s/1X-ruUvzP… Extraction code: DJ9h

This is a computer capture tool, support capture a variety of packets, TCP,UDP,HTTP support. If you’re doing low-level network data testing, you’ll need it. As an interface test, the software is a bit unfriendly. Because the data is refreshed too quickly, it is difficult to locate the interface corresponding to each operation. So, we’re not going to do too much

Introduce the tool.

4.SoupUI

SoapUI is an open source testing tool that uses SOAP/HTTP to examine, invoke, and implement functionality/load/conformance tests for Web services. The tool can be used either as a standalone test software or as a plug-in integrated into Eclipse, Maven2.x, Netbeans, and Intellij.

SoapUI is a free and open source cross-platform functional testing solution. With an easy-to-use graphical interface and enterprise-class capabilities, SoapUI makes it easy to quickly create and perform automated functional, regression, compliance, and load tests. In a test environment, SoapUI provides complete test coverage and supports all tests

There are standard protocols and technologies.

SoapUI is Java based, supports multiple platforms and is easy to install.

This is an open source free and enterprise version of the charge software. In foreign interface testing, use very much. The tool supports interface automation testing and interface performance testing, as well as continuous integration testing with Jenkins. Learn about it, you can download a community free version, do a demo to try.

5.Java code interface tests

Code is omnipotent, and note-taking tools are also developed by code. Why use code to automate interface testing. Because some of the tools are limited, and many companies need some specific features that the tools don’t support, so they have to use code for development. Java is generally used for automated testing, mainly using HttpClient.jar

This package then develops test cases using unit testing tools such as junit or Testng, and then creates a job on Jenkins for continuous integration testing.

6. Do interface tests for Python code

As with Java, Python makes it easy to create interface automation use cases using requests, a nice, powerful third-party library. Unittest is generally used as the unittest framework in python. To generate a test report, htmltestrunner.py is generally selected. Also, you can do continuous integration testing with Jenkins.

7.LoadRunner

Don’t think that LR can only do performance testing, loadRunner can also do interface automation and interface stress testing. It’s just that a lot of us don’t use LR’s functions for development interface test cases.

8.JMeter

JMeter, like LoadRunner, is known for its performance testing, and is generally used for interface performance testing. For example, Java +Jmeter+ Ant + Jenkins do interface performance monitoring tests.

The above introduction of so many tools, the basic coverage of the interface function test, interface automation test, interface performance test.


Python Interface Automation Communication group: 984942724

Your affirmation is my motivation for progress. If you feel good, please encourage! Remember to point wave recommendation oh!! (Click on the ball on the right! (^__^) Hee hee…

Personal public account

Wechat group (the wechat group has reached 100, you can add Hongge’s wechat to pull you into the group, please note: enter the group)