When selecting a tool it is important to understand that carrying a load test, we test not the GUI representation of our application but create a load on the server, which is responsible for the functionality we need. A load testing tool simply "embedded" in their conversation.
And if it does not understand the language of communication (JDBC / FTP / LDAP / SOAP / JMS / POP3 / HTTP / TCP), then we cannot use it. For example, with JMeter you can test web services and http requests, but in communicating between client and the server via tcp / ip protocol can no longer interfere.
All the instruments in principle the same by the structure and consist of the following components:
recorder - records the actions performed by users according to test scenarios, and turns them into software code;
code IDE - Development Environment;
generator - the very thing that creates virtual users performing the described test scenarios;
analyzer - the analyzer of test results.
There are a lot of performance testing tools. Here are the main:
Apache Jmeter. The tool is free, what is perhaps its main advantage and reason for the popularity. Tool, in general, quite good and it is fully functional, although not the most convenient interface. Here is the script:
Unfortunately, this tool has a lot of problems and limitations, but in general, JMeter is a good tool for solving not the biggest and most complex tasks with a modest budget.
HP LoadRunner. Unlike the previous tool, LoadRunner has more merit, but the biggest weakness is a very serious price. However, LoadRunner has a better interface, has more features, a built-in monitoring and providing to the results of the tests more meaningful graphics.
There are some other tools:
- Borland SilkPerformer.
- Visual Studio Test tools
- Oracle Automation Testing Suites (OATS).