Scenario: Stress testing the Web app and MySQL database using JMeter
JMeter is a very powerful test tool that can be used to test the Web, database, since 07 has been used for it has been a unique, the following record in a project on its simple use.
Project Sub-database testing and Web application testing
Database testing is relatively simple, the JDBC driver of the database to be tested is placed into the JMeter Lib folder, a new thread group, 100 threads configured, 10 cycles, 10 seconds to start all threads, and a JDBC connection configuration, Add the crud action you want to make, click the Start button, and then look at performance through the summary report.
Set up a thread group, start 100 threads (10s), each thread loops through all steps 10 times, and a step error continues:
JDBC Connection configuration:
In Crud C, because some fields of data require uniqueness, a counter (counter) is added to guarantee the uniqueness of the field in the database:
Counter:
Execution Ctrl+r, in summary report can see the test data summary
You can see the interaction of each request in the view result tree to facilitate debug
More debug, you can use the JMeter interface, Options-"Log viewer to help debug JMeter runtime problems encountered, want to display more log in the log viewer, You can modify the Jmeter.properties under the Bin folder
log_level.jmeter=info
Log_level.jmeter.junit=debug
#log_level. Jmeter.control=debug
#log_ Level.jmeter.testbeans=debug
#log_level. Jmeter.engine=debug
#log_level. Jmeter.threads=debug
#log_ Level.jmeter.gui=warn
#log_level. Jmeter.testelement=debug
#log_level. Jmeter.util=warn
#log_ Level.jmeter.util.classfinder=warn
#log_level. Jmeter.test=debug
#log_level. Jmeter.protocol.http=debug
# for Cookiemanager, AuthManager etc:
#log_level. Jmeter.protocol.http.control=debug
#log_ Level.jmeter.protocol.ftp=warn
#log_level. Jmeter.protocol.jdbc=debug
#log_level. jmeter.protocol.java= WARN
#log_level. Jmeter.testelements.property=debug
Log_level.jorphan=info