Table of contents
1. Introduction to PostManEdit
3. The difference between Postman and Jmeter
1. Differences in development languages:
2. Differences in scope of use:
5. Simple Tutorial on Jmeter Stress Testing
6. QTP (Quick Test Professional) installation detailed tutorial
1. Introduction to PostMan
Postman is a commonly used interface testing tool. Compared with other interface testing tools, such as Jmeter, RESTClient, loadrunner, SoapUI, etc., it is a relatively simple interface testing tool.
1. Postman is a super powerful testing tool for sending HTTP requests
2. A common tool for people who develop and test WEB pages
3. Create and send any HTTP request (Get/Post/Put/Delete... )
Available to both developers and testers:
1) Developers: After developing the interface of each function, you need to debug it yourself first;
2) Testers: Test whether the interface is implemented correctly by setting different parameters;
In fact, Postman is a tool that developers use more. Because testers will have more choices for interface testing, such as Jmeter, soapUI, etc., Postman is relatively simple, convenient, and powerful.
2. Download and install
Official website: Download Postman | Get Started for Free
Go to the official website to download the corresponding version, click download directly, and the following exe file will be downloaded soon. Just click to install. There is no installation path, etc., and its icon will be directly on the desktop.
Run - double-click the icon, follow the prompts to register on the webpage (limited registration is enough), and then return to the app to log in directly
3. The difference between Postman and Jmeter
1. Differences in development languages:
Postman is an interface testing tool written in js language.
Jmeter is a pure UI interface + performance testing tool written in Java language.
2. Differences in scope of use:
Postman can generally only do interface testing, while Jmeter can also do performance testing in addition to interface testing .
3. Differences in use:
When Postman enters interface information, the URL is a whole, while Jmeter is split into four parts (protocol name, IP address, path, port number)
Postman can add request header information directly to the request, Jmeter needs to add a header manager (Http header manager)
Although Postman can also load test cases through csv files, it needs to manually load test data every time it is started, which cannot fully realize automation. When Jmeter loads test data from csv files, it does not need to be loaded manually and can realize interface automation.
Postman assertions require writing js scripts, and there is no encapsulated assertion method. Jmeter encapsulates a variety of assertion methods. Generally, users do not need to write BeanShell scripts to implement assertions.
Postman does not have a logical controller, while Jmeter has a logical controller, which makes the application more flexible.
Postman needs to download and install the third-party plug-in xmysql to connect to the database. Jmeter comes with a plug-in for linking to the database. And in terms of data processing, Jmeter is easier to understand and operate.
4. Jmeter installation
Attached is a detailed Jmeter usage tutorial for beginners. Thanks to the author, it is effective in personal testing.
https://www.cnblogs.com/echolun/p/10003985.html
Change to permanent Chinese: