There are many articles in the forum that introduce how to use JMeter for interface testing (API testing) . About 40.67% of the surveyed testers use JMeter as an automated testing tool for interface testing (ranked among commercial or open source tools) The first among them), the rest are Postman (28%), and SoapUI (17.33%).
However, it is worth noting that 44.13% of them adopted self-developed tools, indicating that the existing open source tools may not meet the needs, and more of them adopted self-developed methods. So today we will take a look at the advantages and disadvantages of JMeter for interface testing, and how to solve this problem.
- Advantages of JMeter Interface Testing
1) JMeter is relatively lightweight, open source, highly accepted by the community, and relatively easy to get started.
2) JMeter provides BeanShell programming capability, which can write more flexible test scripts.
3) The JMeter community is relatively complete and provides rich protocol support. For example, in addition to supporting the common HTTP protocol, you can also directly connect to the database through JDBC Sampler, store the expected test results in the database, and directly verify the test results. In the process of writing test scripts, different protocol calls can be combined with the same script to write more complex test cases.
4) JMeter provides relatively advanced extension capabilities, allowing you to define and expand new protocol support, such as extending the JMeter plug-in that supports the Dubbo protocol provided by Ali.
5) JMeter provides the ability to integrate HTML test reports and Jenkins, which makes it easier to implement some basic continuous testing.
- Shortcomings of JMeter interface testing
As an interface testing solution, JMeter probably has the following problems:
1) Script flexibility. Although JMeter provides certain BeanShell programming capabilities and custom protocol extension capabilities, which allow script developers to have a certain degree of flexibility, subject to the limitations of JMeter itself, compared with developers directly using the language for interface testing, the flexibility is still Relatively insufficient.
2) Ability to report. JMeter provides HTML reports, but JMeter's own test reports are mainly used for performance testing, reflecting more results at the performance testing level. Moreover, the configuration process is more complicated, and it is more troublesome in sharing reports among team members.
3) Continuous integration. Using third-party Jenkins plug-ins, Ant and Maven, etc., some basic continuous test integration with JMeter can be performed, but there is insufficient support for the management of the test environment required for complete automation, and the configuration process is a bit cumbersome.
4) Management of test scripts and test results: scripts and results are basically managed locally and cannot be managed online.
- Optimized JMeter interface test scheme
An ideal JMeter-based interface testing solution can make up for the above disadvantages, including the need to make up for the shortcomings at the level of the team and tools.
The problem of insufficient flexibility of JMeter scripts can be solved through reasonable collocation of team members. JMeter provides a relatively complete extension mechanism, which can support different protocols and functions through extensions. The plug-ins and functions processed by these extensions can make writing test scripts easier. The extension of JMeter requires a good understanding of Java and the extension mechanism of JMeter. The extension development of JMeter is one-time. After the development of the plug-in is completed, the script writer will write the script based on the extended plug-in and function, so as to quickly complete the interface test. Therefore, a better team match is:
1) One or more test developers who understand JMeter extensions are mainly responsible for the implementation of related extension functions, as well as the definition of reports and some development work related to continuous integration.
2) JMeter test script writers are mainly responsible for the script development based on JMeter's built-in and custom extension plug-ins. If it is found that sometimes it is inconvenient in the script development process, submit the development requirements and the test developer will extend JMeter.
The rest of the solution required test reports, continuous test integration, test scripts and result management require some additional customization work to meet the needs.
The following are supporting learning materials. For friends who do [software testing], it should be the most comprehensive and complete preparation warehouse. This warehouse also accompanied me through the most difficult journey. I hope it can help you too!
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
Information acquisition method:
