Vista previa parcial del texto
¡Descarga Gestión de Proyectos y más Esquemas y mapas conceptuales en PDF de Gestión de Proyectos solo en Docsity!
1. Getting Started 1.0 Overview When using JMeter you will usually follow this process: 1.0.1 Test plan building To do that, you will run JMeter in GUI Mode Then you can either choose to record the application from a browser, or native application. You can use for that the menu File — Templates... — Recording Note you can also manually build your plan. Ensure you read this documentation to understand major concepts You will also debug it using one of these options: * Run = Start no pauses * Run = Start « Validate on Thread Group and View Results Tree renderers or Testers (CSS/JQUERY, JSON, Regexp, XPath). Ensure you follow best-practices when building your Test Plan 1.0.2 Load Test running Once your Test Plan is ready, you can start your Load Test. The first step is to configure the injectors that will run JMeter, this as for any other Load Testing tool includes: Correct machine sizing in terms of CPU, memory and network OS Tuning Java setup: Ensure you install the latest version of Java supported by JMeter Increase the Java Heap size. By default JMeter runs with a heap of 1 GB, this might not be enough for your test and depends on your test plan and number of threads you want to run Once everything ¡is ready, you will use CLl mode (Command-line mode previously called Non-GU! mode) to run it for the Load Test. Don't run load test using GUI mode ! Using CL! mode, you can generate a CSV (or XML) file containing results and have JMeter generate an HTML report at end of Load Test. JMeter will by default provide a summary of load test while it's running. You can also have real-time results during your test using Backend Listener 1.0.3 Load Test analysis Once your Load Test is finished, you can use the HTML report to analyze your load test 1.0.4, Let's start The easiest way to begin using JMeter ¡is to first download the latest production release and install it The release contains all of the files you need to build and run most types of tests, e g. Web (HTTP/HTTPS), FTP, JDBC, LDAP, Java, JUnit and more If you want to perform JDBC testing, then you will, of course, need the appropriate JDBC driver from your vendor. JMeter does not come with any JDBC drivers. JMeter includes the JMS API jar, but does not include a JMS client implementation. If you want to run JMS tests, you will need to download the appropriate jars from the JMS provider See the JMeter Classpath section for details on installing additional jars. Next, start JMeter and go through the Building a Test Plan section of the User Guide to familiarize yourself with JMeter basics (for example, adding and removing elements) Finally, go through the appropriate section on how to build a specific type of Test Plan. For example, if you are interested in testing a Web application, then see the section Building a Web Test Plan. The other specific Test Plan sections are Advanced Web Test Plan JDBC FIP JMS Point-to-Point JMS Topic LDAP LDAP Extended WebsServices (SOAP) Once you are comfortable with building and running JMeter Test Plans, you can look into the various configuration elements (timers, listeners, assertions, and others) which give you more control over your Test Plans. 1.1 Requirements JMeter requires that your computing environment meets some minimum requirements 1.1.1 Java Version JMeter is compatible with Java 8 or higher. We highly advise you to install latest minor version of your major version for security and performance reasons Because JMeter uses only standard Java APIs, please do not file bug reports if your JRE fails to run JMeter because of JRE implementation issues. Although you can use a JRE, it is better to install a JDK as for recording of HTTPS, JMeter needs keytoo1 utility from JDK. 1.1.2 Operating Systems JMeter is a 100% Java application and should run correctly on any system that has a compliant Java implementation Operating systems tested with JMeter can be viewed on this page on JMeter wiki. Even if your OS ¡s not listed on the wiki page, JMeter should run on it provided that the JVM is compliant 1.2 Optional Ifyou plan on doing JMeter development, then you will need one or more optional packages listed below. E 1.2.1 Java Compiler If you want to build the JMeter source or develop JMeter plugins, then you will need a fully compliant JDK 8 or higher. 1.2.2 SAX XVIL Parser JMeter comes with Apache's Xerces XML parser You have the option of telling JMeter to use a different XML parser. To do so, include the classes for the third-party parser in JMeter's classpath, and update the ¡meter properties file with the full classname of the parser implementation. 1.2.3 Email Support JMeter has extensive Email capabilities. lt can send email based on test results, and has a POP3(S/IMAP(S) sampler. It also has an SMTP(S) sampler. 1.2.4 SSL Encryption To test a web server using SSL encryption (HTTPS), JMeter requires that an implementation of SSL be provided, as is the case with Sun Java 1.4 and above. lf your version of Java does not include SSL support, then it is possible to add an external implementation. Include the necessary encryption packages in JMeter's classpath. Also, update system. properties to register the SSL Provider JMeter HTTP defaults to protocol level TLS. This can be changed by editing the JMeter property https.default.protocol IN jmeter. properties Ol user.properties The JMeter HTTP samplers are configured to accept all certificates, whether trusted or not, regardless of validity periods, etc. This ¡is to allow the maximum flexibility in testing servers. Ifthe server requires a client certificate, this can be provided. There is also the SSL Manager, for greater control of certificates The JMeter proxy server (see below) supports recording HTTPS (SSL) The SMTP sampler can optionally use a local trust store or trust all certificates 1.2.5 JDBC Driver You will need to add your database vendor's JDBC driver to the classpath if you want to do JDBC testing. Make sure the file is a jar file, not a zip 1.2.6 JMS client JMeter now includes the JMS API from Apache Geronimo, so you just need to add the appropriate JMS Client implementation jar(s) from the JMS provider. Please refer to their documentation for details. There may also be some information on the JMeter Wiki 1.2.7 Libraries for ActiveMQ JMS You will need to add the jar activemq-a11-X.X.X.jar to your classpath, e.g. by storing ¡tin the 1ib/ directory. See ActiveMQ initial configuration page for details. See the JiMeter Classpath section for more details on installing additional jars 3 Installation We recommend that most users run the latest release To install a release build, simply unzip the zip/tar file into the directory where you want JMeter to be installed. Provided that you have a JRE/JDK correctly installed and the JAVA_HOME environment variable set, there is nothing more for you to do There can be problems (especially with client-server mode) if the directory path contains any spaces. The installation directory structure should look something like this (where X.Y is version number): You can rename the parent directory (8. apache-jmeter-X. Y) if you want, but do not change any of the sub-directory names 1. ¿ Running JMeter To tim run JMeter, run the jmeter.bat (for Windows) 0! jmeter (for Unix) file. These files are found in the bin directory. After a short e, the JMeter GU! should appear. GUI mode should only be used for creating the test script CLI mode (NON GUI) must be used for load testing There are some additional scripts in the bin directory that you may find useful. Windows script files (the .CMD files require Win2K or later): jmeter.bat run JMeter (in GUI mode by default) jmeterw.cmd run JMeter without the windows shell console (in GUI mode by default) jmeter-n.cmd drop a JMX file on this to run a CLI mode test jmeter=n-".cmd drop a JMX file on this to run a CLI mode test remotely jmeter-t.cmd drop a JMX file on this to load it in GUI mode jmeter-server.bat start JMeter in server mode mirror-server.cmd runs the JMeter Mirror Server in CLl mode shutdown. cmd Run the Shutdown client to stop a CLl mode instance gracefully stoptest.cmd Run the Shutdown client to stop a CLl mode instance abruptly The special name LAsT can be used With jmeter-n.cmd, jmeter-t.cmd ANA jmeter-n-r.cmd and means the last test plan that was run interactively There are a few environment variables, that can be used to customize the JVM settings for JMeter. An easy way to set those ¡is by cre ating a file named setenv.bat in the bin directory. Such a file could look like The JVM_ARGS can be used to override JVM settings in the jmeter.bat script and will get set when starting JMeter, e.g. The following environment variables can be defined: DDRAWN JVM options to influence usage of direct draw, e.9. -Dsun.java2d.ddscale=true. Default is empty. GC_ALGO JVM garbage collector options. Defaults to -XX:+UseG1GC -XX:MaxGCPauseMillis=250 -XX:GlReservePercent=20 HEAP JVM memory settings used when starting JMeter. Defaults to -Xmslg -Xmxlg -XX:MaxMetaspaceSize=256m JIMETER_BIN JMeter bin directory (must end in 1). Value will have been guessed, when setenv. bat ¡s Called JIMETER_COMPLETE_ARGS If set indicates, that JVM_ARGS and JMETER_OPTS are to be used, only. All other options like HEAP and GC_ALGO will be ignored Default is empty IMETER_HOME installation directory. Will be guessed from location Of jmeter.bat IMETER_LANGUAGE Java runtime options to specify used language Defaults to: -Duser.language="en" -Duser.region="EN" JM_LAUNCH Name of the java executable, like java.exe (default) OT javaw. exe JVM_ARGS Java options to be used when starting JMeter. These will be added last to the java command. Default is empty Un*x script files; should work on most Linux/Unix systems jmeter run JMeter (in GUI mode by default). Defines some JVM settings which may not work for all JUMs jmeter-server start JMeter in server mode (calls jmeter script with appropriate parameters) jmeter.sh very basic JMeter script (fou may need to adapt JVM options like memory settings). mirror-server.sh runs the JMeter Mirror Server in CLl mode shutdoun.sh Run the Shutdown client to stop a CLI mode instance gracefully stoptest.sh Run the Shutdown client to stop a CLI mode instance abruptly lt may be necessary to set a few environment variables to configure the JVM used by JMeter. Those variables can be either set directly he shell starting the jmeter script For example setting the variable JVM_ARGS will override most pre-defined settings, for example in t will override the HEAP settings in the script. To set those variables permanently, you can place them in a file called setenv.sh in the bin directory. This file will be sourced when run ning JMeter by calling the jmeter script. An example for bin/setenv.sh Could look like The following environment variables can be defined: GC_ALGO Java runtime options to specify JVM garbage collection algorithm. Defaults to -XX:+UseG1GC -XX:MaxGCPauseMillis=259 - XX: GlReservePercent=20 HEAP Java runtime options for memory management used when JMeter is started. Defaults to -Xmslg -Xmxlg - X:MaxMetaspaceSize=256m JAVA_HOME Must point at your Java Development Kit installation. Required to run the with the "debug" argument On some OSes it JMeter will try its best to guess the location of the JVM. IMETER_COMPLETE_ARGS If set indicates, that JVM_ARGS and JMETER_OPTS are to be used, only. All other options like HEAP and GC_ALGO will be ignored Default is empty. IMETER_HOME May point to your JMeter install dir. 1f empty it will be set relative to the jmeter script IMETER_LANGUAGE Java runtime options to specify used language. Defaults lo -Duser.languageszen -Duser.region=EN IMETER_OPTS Java runtime options used when JMeter is started. Special options for operating systems might be added by JMeter. JRE_HOME Must point at your Java Runtime installation. Defaults to JAVA_HOME if empty. If JRE_HOME and JAVA_HOME are both empty, JMeter will try to guess JAVA_HOME. If JRE_HOME and JAVA_HOME are both set, JAVA_HOME ¡s used. JVM_ARGS Java options to be used when starting JMeter. These will be added before JMETER_OPTS and after the other JVM options. Default is empty 1.4.1JMeter's Classpath JMeter automatically finds classes from jars in the following directories: IMETER_HOME/1lib used for utility jars JIMETER_HOME/1ib/ext used for JMeter components and plugins Ifyou have developed new JMeter components, then you should jar them and copy the jar into JMeter's 1ib/ext directory JMeter will automatically find JMeter components in any jars found here. Do not use 1ib/ext for utility jars or dependency jars used by the plugins; itis only intended for JMeter components and plugins. Ifyou don't want to put JMeter plugin jars in the 1ib/ext directory, then define the property search_paths in jmeter.properties. Utility and dependency jars (libraries etc) can be placed in the 1ib directory If you don't want to put such jars in the 1ib directory, then define the property user.classpath Or plugin_dependency_paths ÍN jmeter.properties. See below for an explanation of the differences. Other jars (such as JDBC, JMS implementations and any other support libraries needed by the JMeter code) should be placed in the 1ib directory - not the 1ib/ext directory, or added to user.classpath JMeter will only find .jar files, not .zip. You can also install utility Jar files in $3AVA_HOME/jre/lib/ext, or you can set the property user. classpath in jmeter.properties Note that setting the CLASSPATH environment variable will have no effect. This is because JMeter is started with "java -jar", and the java command silenily ignores the CLASSPATH variable, and the -classpath!-cp options when -jar is used. This occurs with all Java programs, not just JMeter. 1.4.2 Create Test Plan from Template You have the ability to create a new Test Plan from existing template To do so you use the menu File — Templates... or Templates icon: File Edit Search Run Options Help paja 50 |+ -= 2 Pb a [estPan] | Test Plan Comments: Templates icon item A popup appears, you can then choose a template among the list: Templates Select Template [Recording [y] Reload templates Template showing how to record JMeter Configuration a JMeter Server Proxy port is set to 8888, you may want to change this Browser Configuration Configure your browser so that it uses the JMeter proxy, set: sw the host of the machine that runs JMeter se the port you setup in JMeter Server Proxy Useful links e http: //jmeter.apache.org/fusermanual'jmeter proxy step by step.pdi e http: //jmeter.apache.org/usermanual/component_reference.html*HTTP_Proxy_Server Create Cancel Templates popup Some templates may need parameters input from the user. For theses ones, after a click on the create button, a new window will appear as follow * [6] Templates x 3 1) NE pi OS Parameters window When you are done with parameters, click on the Validate button and the template will be created A documentation for each template explains what to do once test plan is created from template. You can create your own templates following documentation here 1.4.3 Using JMeter behind a proxy If you are testing from behind a firewall/proxy server, you may need to provide JMeter with the firewall/proxy server hostname and port number. To do so, run the jmeter[ .bat] file from a command line with the following parameters + [proxy scheme to use - optional - for non-http] a [proxy server hostname or ip address] hi [proxy server porl] Ni [nonproxy hosts] (e.9. *.apache.org|localhost) Ss [username for proxy authentication - if required] P [password for proxy authentication - if required] Example: You can also use - -proxyScheme, --proxyHost, --proxyPort, --username, aNd --passuord as parameter names Parameters provided on a command-line may be visible to other users on the system Ifthe proxy scheme is provided, then JMeter sets the following System properties * http.proxyScheme Ifthe proxy host and port are provided, then JMeter sets the following System properties: * http.proxyHost * http.proxyPort * https.proxyHost * https.proxyPort The user and password used for a proxy can be given by the System properties http.proxyUser and http.proxyUser. They will get overridden by the above arguments or values set in the HTTP Samplers. Ifa nonproxy host list is provided, then JMeter sets the following System properties: * http.nonProxyHosts * https.nonProxyHosts So if you don't wish to set both http and https proxies, you can define the relevant properties in system.properties instead of using the command-line parameters Proxy Settings can also be defined in a Test Plan, using either the HTTP Request Defaults configuration or the HTTP Request sampler elements JMeter also has ¡ts own in-built Proxy Server, the HTTP(S) Test Script Recorder. This is only used for recording HTTP or HTTPS browser sessions. This is not to be confused with the proxy settings described above, which are used when JMeter makes HTTP or HTTPS requests itself. 1.4.4 CLI Mode (Command Line mode was called NON GUI mode) For load testing, you must run JMeter in this mode (Without the GUI) to get the optimal results from it. To do so, use the following command options n This specifies JMeter is to run in cli mode + [name of JMX file that contains the Test Plan] a [name of JTL file to log sample results to] . [name of JMeter run log file]. ” Run the test in the servers specified by the JMeter property "remote_hosts” a [list of remote servers] Run the test in the specified remote servers :5 [path to CSV file] generate report dashboard only generate report dashboard after load test o output folder where to generate the report dashboard after load test. Folder must not exist or be empty The script also lets you specify the optional firewall/proxy server information: -H [proxy server hostname or ip address] -P [proxy server porl] Example Ifthe property jmeterengine.stopfail.system.exit is setto true (default is false), then JMeter will invoke System.exit(1) ¡fit cannot stop all threads. Normally this is not necessary. 1.4.5 Server Mode For distributed testing, run JiMeter in server mode on the remote node(s), and then control the server(s) from the GUI. You can also use CLI mode to run remote tests. To start the server(s), TUN jmeter-server[ .bat] on each server host The script also lets you specify the optional firewall/proxy server information: -H [proxy server hostname or ip address] -P [proxy server parl] Example: Ifyou want the server to exit after a single test has been run, then define the JMeter property server.exitaftertest=true To run the test from the client in CLI mode, use the following command: where: 6 is used to define JMeter properties to be set in the servers Xx means exit the servers at the end of the test -Rserverl,server2 can be used instead of -r to provide a list of servers to start. Overrides remote_hosts, but does not define the property. lIfthe property jmeterengine. remote. system.exit ¡is setlo true (default is false), then JMeter will invoke System.exit(0) after stopping RMI at the end of a test. Normally this is not necessary. 1.4.6 Overriding Properties Via The Command Line Java system properties and JMeter properties can be overridden directly on the command lin (instead of modifying jmeter.properties) To do so, use the following options: -D[prop_name]=[value] defines a java system property value. -J[prop_name]=[value] defines a local JMeter property: -G[prop_name]=[value] defines a JMeter property to be sent to all remote servers. -G[propertyfile] defines a file containing JMeter properties to be sent to all remote servers -L[category]=[priority] overrides a logging setting, setting a particular category to the given priority level The -L flag can also be used without the category name to set the root logging level. Examples: The command line properties are processed early in startup, but after the logging system has been set up 1.4.7 Logging and error messages Since 3.2, JMeter logging is not configured through properties file(s) such as jmeter.properties any more, but it is configured through a Apache Log4; 2 configuration file (log432.xm1 in the directory from which JMeter was launched, by default) instead. Also, every code including JMeter and plugins MUST use SLF4J library to leave logs since 3.2 Here is an example log432.xm1 file which defines two log appenders and loggers for each category So, if you want to change the log level for arg.apache.http category to debug level for instance, you can simply add (or uncomment) the following logger element in 10g432.xm1 file before launching JMeter. For more detail on how to configure log432.xm1 file, please see Apache Log4;¡ 2 Configuration page Log leve! for specific categories or root logger can be overridden directly on the command line (instead of modifying log432.xm1) as well. To do so, use the following options -L[category]=[priority] Overrides a logging setting, setting a particular category to the given priority level. Since 3.2, it is recommended to use a full category name (e.9, org.apache.jmeter Ol com.example.foo), but if the category name starts with either jmeter Or jorphan, org.apache. Will be prepended internally to the category name input to construct a full category name (¡.e, org.apache.jmeter Of org.apache.jorphan) for backward compatibility m > fo a m a Differences in Logging : Old vs New Practices: As JMeter uses SLF4J as logging API and Apache Log4; 2 as a logging framework since 3.2, not every log level used before 3.2 can match exactly with one of the new available log levels provided by SLF4J/Log4j2. Therefore, please keep the following differences and new suggested practices in mind if you need to migrate any existing logging configurations and logging code Category Old Practices Before 3.2 New Practices Since 3.2 Logger Logger reference through LoggingManager: Use SLF4J API with either category or explicit class: Log Levels in Old Log Levels: Mapping to New Levels through SLF4J/Log4j2 Configuration or Command +» DEBUG - DEBUG Line . INFO * INFO Arguments = WARN + LARN » ERROR + ERROR + FATAL_ERROR + ERROR = NONE * OFF Since FATAL_ERROR ¡s not supported by SLF4J API, itis treated as ERROR instead for existing code not to break. There ¡s also the FATAL log level option TRACE level, which is less specific than DEBUG, ¡is supported additionally since 3.2 Look up SLF4J or Apache Log4J 2 documentations for details. JMeter does not generally use pop-up dialog boxes for errors, as these would interfere with running tests. Nor does it report any error for a mis-spelt variable or function; instead the reference is just used as is. See Functions and Variables for more information. If JMeter detects an error during a test, a message will be written to the log file. The log file name ¡s defined in the log432.xm1 file (or using the -¿ option, see below). It defaults to jmeter. log, and will be found in the directory from which JMeter was launched The menu Options —= Log Viewer displays the log file in a bottom pane on main JMeter window In the GUI mode, the number of error/fatal messages logged in the log file is displayed at top-right Error/fatal counter The command-line option -j jmeterlogfile allow to process after the initial properties file is read, and before any further properties are processed. lt therefore allows the default of jmeter. log to be overridden. The ¡meter scripts that take a test plan name as a parameter (e.9. jmeter-n.cmd) have been updated to define the log file using the test plan name, e.g. for the test plan Test27.jmx the log file is setto Test27.log. When running on Windows, the file may appear as just ¡meter unless you have set Windows to show file extensions. [Which you should do anyway, to make it easier to detect viruses and other nasties that pretend to be text files ...] As well as recording errors, the jmeter. log file records some information about the test run. For example: Ba] The log file can be helpful in determining the cause of an error, as JMeter does not interrupt a test to display an error dialogue. 1.4.8 Full list of command-line options Invoking JMeter as "jmeter ->?" will print a list of all the command-line options. These are shown below. Ba] Note: the JMeter log file name ¡is formatted as a SimpleDateFormat (applied to the current date) if it contains paired single- quotes, .e.9. 'jmeter_'yyyyMMddHHmmss'.log' Ifthe special name LAST ¡s used for the -t, -j or -1 flags, then JMeter takes that to mean the last test plan that was run in interactive mode 1.4.9 CLI mode shutdown Prior to version 2.5.1, JMeter invoked System.exit() when a CLl mode test completed. This caused problems for applications that invoke JMeter directly, so JMeter no longer invokes System.exit() for a normal test completion. [Some fatal errors may still invoke System. exit()] JMeter will exit all the non-daemon threads it starts, but it is possible that some non-daemon threads may still remain; these will prevent the JVM from exiting. To detect this situation, JMeter starts a new daemon thread just before it exits. This daemon thread waits a short while; ¡fit returns from the wait, then clearly the JVM has not been able to exit, and the thread prints a message to say why The property jmeter.exit.check.pause Can be used to override the default pause of 2000ms (2secs). If set to e, then JMeter does not start the daemon thread 1.5 Configuring JMeter Ifyo: crea The SS See u wish to modify the properties with which JMeter runs you need to either modify the user.properties in the /bin directory or te your own copy ofthe jmeter.properties and specify it in the command line. Note: You can define additional JMeter properties in the file defined by the JMeter property user.properties which has the default value user.properties. The file will be automatically loaded if it is found in the current directory or if it is found in the JMeter bin directory. Similarly, system. properties ¡is used to update system properties Parameters Attribute Description Required ssl provider You can specify the class for your SSL implementation if you don't No want to use the built-in Java implementation xml.parser You can specify an implementation as your XML parser. The default No value ¡s: org.apache.xerces.parsers.SAXParser remote_hosts Comma-delimited list of remote JMeter hosts (or host: port if No required). If you are running JMeter in a distributed environment, list the machines where you have JMeter remote servers running. This will allow you to control those servers from this machine's GUI noí_in_menu Alist of components you do not want to see in JMeter's menus. As No JMeter has more and more components added, you may wish to customize your JMeter to show only those components you are interested in. You may list their classname or their class label (the string that appears in JMeter's Ul) here, and they will no longer appear in the menus search_paths List of paths (separated by ; ) ihat JMeter will search for JMeter No plugin classes, for example additional samplers. A path item can either be a jar file or a directory. Any jar file in such a directory will be automatically included in search_paths, jar files in sub directories are ignored. The given value is in addition to any jars found in the lib/ext directory. user classpath List of paths that JMeter will search for utility and plugin dependency No classes. Use your platform path separator to separate multiple paths. A path item can either be a jar file or a directory Any jar file in such a directory will be automatically included in user.classpath, jar files in sub directories are ignored. The given value is in addition to any jars found in the lib directory. All entries will be added to the class path of the system class loader and also to the path of the JMeter internal loader. plugin_dependency_pat List of paths (separated by ;) ihat JMeter will search for utility and No hs plugin dependency classes. A path item can either be a jar file or a directory. Any jar file in such a directory will be automatically included in plugin_dependency_paths, jar files in sub directories are ignored. The given value ¡is in addition to any jars found in the 1ib directory or given by the user.classpath property. All entries will be added to the path of the JMeter internal loader only. For plugin dependencies using plugin_dependency_paths should be preferred Over user.classpath user properties Name of file containing additional JMeter properties. These are No added after the initial property file, but before the -q and -J options are processed. system properties Name of file containing additional system properties. These are No added before the -s and -D options are processed. command line options and properties files are processed in the following order: -p propfile jmeter.properties (or the file from the -p option) is then loaded -j logfile Logging ¡s initialised user. properties ¡s loaded system.properties ¡s loaded all other command-line options are processed also the comments in the jmeter.properties, user.properties and system.properties files for further information on other settings you can change. 
