"Test" briefly describes the characteristics and functions of several test tools _ testing Tools

Jmeter Apache Jmeter is a Java based stress testing tool developed by the Apache organization. Used to stress test the software, which was originally designed for web application testing, but later extended to other test areas. It can be used to test static and dynamic resources, such as static files, Java applets, CGI scripts, Java objects, databases, FTP servers, and so on. JMeter can be used to simulate a huge load on servers, networks, or objects, test their strength and analyze overall performance from different pressure categories. In addition, JMeter is able to perform functional/regression testing of the application by creating a script with assertions to verify that your program returns the results you expect.         For maximum flexibility, JMeter allows the use of regular expressions to create assertions. Apache JMeter can be used to test the performance of static and dynamic resources (files, Servlet,perl scripts, Java objects, databases and queries, FTP servers, and so on). It can be used to simulate heavy loads on servers, networks, or objects to test their strength or to analyze overall performance under different pressure types. You can use it to do a graphical analysis of performance or to test your server/script/object in a large concurrency load.

JMeter 1. Ability to perform pressure and performance tests on HTTP and FTP servers, and to test any database (via JDBC).        2. Full portability and 100% pure java.        3. Full Swing and lightweight component support (precompiled jar using javax.swing.*) package.        4. A full multithreaded framework allows concurrent sampling through multiple threads and simultaneous sampling of different functions through a separate thread group.        5. Careful GUI design allows for quick operation and more precise timing. 6. Caching and off-line analysis/playback test results.

High scalability of the JMeter 1. A linked sampler allows unlimited testing capabilities.        2. The various load tables and the linked timers are available to choose from.        3. Data analysis and visualization plug-ins provide good scalability and personalization.        4. With the ability to provide dynamic input to the test (including JavaScript).        5. A sampler that supports scripting (1.9.2 and above supports BeanShell). In the design phase, JMeter can act as an HTTP proxy (proxy) to record Ie/netscape HTTP requests, or log files of Apache and other webserver to reproduce HTTP traffic. When these HTTP client requests are logged, the test run can easily set the number of repetitions and concurrency (threads) to generate significant traffic. JMeter also provides visual components and reporting tools to show the performance of the volume server under different pressures. [2] compared with other HTTP test tools, the main feature of JMeter is the strong extensibility. JMeter can automatically scan the plug-ins in the. jar file in its Lib/ext subdirectory and load it into memory, allowing the user to invoke it through a different menu.

Junit

JUnit is a unit-testing framework for the Java language. Founded by Kent Beck and Erich Gamma, it has become the most successful of the Xunit family of Sunit from Kent Beck. JUnit has its own JUnit expansion biosphere. Most Java development environments have integrated junit as a tool for unit testing. [1-2] JUnit is a regression testing framework (regression testing framework) written by Erich Gamma and Kent Beck. JUnit tests are programmer tests, known as white-box tests, because programmers know how the software being tested accomplishes functions and what (What) functions are done. JUnit is a set of frameworks that inherit the TestCase class and can be tested automatically with JUnit.
In addition, JUnit is a highly recommended tool in extreme programming and refactoring (refactor), because in the implementation of automated unit testing can greatly improve the efficiency of development, but actually writing test code also requires a lot of time and effort, then the use of this dongdong benefits in the end. I think this is the case: Extreme programming requires that you write tests before you write code, which forces you to think about the functionality and logic of the code before you write the code, otherwise the code is very unstable, so you need to maintain both the test code and the actual code, which will greatly increase the workload. So in extreme programming, the basic process is this: the idea-> write test code-> write code-> test, and write test and write code is incremental, write a little bit, in the future code if found that the problem can be traced quickly to the cause of the problem, Reduce the difficulty of error correction of regression errors. Refactoring is similar to the benefits of extreme programming, because refactoring also requires a little bit of change to reduce the time consuming caused by regression errors. In other cases, it is also necessary to use JUnit to write some appropriate tests when we are developing, because we are usually the code that needs to write the test, probably not the junit used, if you use JUnit, and writing test code against the interface (method) will reduce future maintenance work, For example, later changes to the internal method (this is the equivalent of refactoring work). In addition, because JUnit has the assertion function, if the test results do not pass will tell us which test does not pass, why, if it is like before the general practice is to write some test code to see its output, and then by themselves to determine whether the results are correct, The benefit of using JUnit is that it's the right thing to do, and we just need to see if it tells us if the results are correct, and it's going to be much more efficient in general.



Testlink

Testlink is a web-based test case management system, the main function is the creation, management and execution of test cases, and also provides some simple statistical functions.
Testlink is used for management during testing, and by using the functionality provided by Testlink, the test process can be fully managed from test requirements, test design, to test execution, and it also provides statistics and analysis of a number of test results. Allows us to simply start the test work and analyze the test results [1]. Testlink is one of the open source projects for SourceForge. As a web-based test management system, the main features of Testlink include:
Test Requirements Management
Test Case Management
Test case coverage management for test requirements
The development of the test plan
Execution of test Cases
The measurement and statistical functions of a large number of test data.
There are currently defects in XLS imports, but you can use a third party Testlink Convert tool to implement Xls/txt/xml import export.

Implementation features
1 according to different project management different test plan, test case, test build mutually independent 2 according to the tree-like project, component, classification, test case, design test Case 3 can search test case 4 based on keywords can be easily modified and reused for existing test cases 5 The same project can develop different test plans, and then assign the same test case to the test plan (you can implement the test case reuse, filter) 6 can set the status of the test execution (pass, fail, lock, not executed), the failed test case can and the bug in the Bugzilla The correlation, each test case executes, may fill in the correlation explanation 7 test result analysis (may realize according to the requirement, according to the test plan, according to the test case state, according to the version, the statistic test result) 8 custom role, through the role control user Permissions 9 test results can export For Excel table 10 test cases can be exported as CSV, HTML format 11 through a hyperlink, you can use the text Format requirements, Plan Association 12 to correspond the test case and test requirements. Tests can be assigned to testers based on priority, defining milestones

LoadRunner
LoadRunner is a load testing tool that predicts system behavior and performance. LoadRunner is able to test the entire enterprise architecture by identifying and locating problems by simulating tens of millions of users in the form of concurrent load and real-time performance monitoring. Enterprises use LoadRunner to minimize test time, optimize performance, and accelerate the release cycle of application systems. LoadRunner can be applied to automated load testing of various architectures to predict system behavior and evaluate system performance.
Advantage:
Enterprise's network application environment must support a large number of users, the network architecture contains all kinds of application environment and different vendors to provide software and hardware products. Unpredictable user loads and increasingly complex application environments cause companies to worry about problems such as slow user response, system crashes, and so on. All this inevitably leads to loss of corporate earnings. Mercury Interactive's LoadRunner enables organizations to protect their sources of revenue by maximizing existing IT resources without acquiring additional hardware and ensuring that end users have a good evaluation of the quality, reliability, and scalability of their testing applications in all aspects of the application system. The LoadRunner test object is the whole enterprise system, by simulating the actual user's operation behavior and implementing real-time performance monitoring, to help enterprise customers find and find problems faster. LoadRunner can support a wide range of protocols and technologies.