Jmeter(外国英文资料).docVIP

Jmeter 1, the use of Jmeter. Jmeter, as a pure Java application, requires an Java environment. For Java environments, you generally need to install JDK, and you need to configure the environment variables. A, new environment variable: JAVA_HOME, and the value is the JDK path of JAVA. C:\Program Files\Java\jdk1.6.0_32 B, modify the environment variable: path, add a value %JAVA_HOME%\bin to path Common sense: Under Windows, references to environment variables are in the form of%VarName%, If an environment variable has multiple values, the value and value are separated by semicolons. Under Linux, references to environment variables are in the form of $VarName. If an environment variable has multiple values, the values and values are separated by colons. 2, a simple understanding of the composition of Jmeter. Bin: the path to the executable program. Jmeter.bat:Jmeter startup program. This program can be modified. The main thing is to modify the JVM settings item in it. Jmeter-server.bat: equivalent to Load Generator in LR. For on-line load. If under Linux, you need to start the server side and use the command. ./Jmeter.sh -s Jperties: is used to configure the properties of Jmeter. Jmeter has more than 80% of the configuration in this file. Lib: This is the default classpath for Jmeter startup. If you need to call the third party jar package in the next test, place it all under that path. New add pack to Lib directory, need to restart Jmeter to read to. Lib\ext: used to store components and plug-ins. Component refers to the GUI interface, you can see some operating objects. In general, the two developments and customization that you do later are placed in this path. 3, Jmeter script development Jmeter script development comes in three ways: 1. Record with badboy 2. Use your own HTTP proxy server to record 3, capture handwritten. Recording with badboy. 1, can not be saved directly. Direct saving is the script of badboy, not the script of Jmeter. The script should be save