【正文】 組件參考 ? 16. 函數(shù) ? 17. 詞匯表 1. 簡介 Apache JMeter 是 100％的 Java桌面應用程序。 它可以用于測試靜態(tài)何動態(tài)資源例如靜態(tài)文件、 Java 小服務程序、 CGI 腳本、 Java 對象、 數(shù)據(jù)庫 ， FTP 服務器 , 等等。 另外， JMeter能夠對應用程序做衰退測試，通過創(chuàng)建帶有 斷言 的腳本來驗證你的程序返回了你期望的結果。 歷史 Apache Software Foundation 的 Stefano Mazzocchi 是 JMeter的最初開發(fā)人員。我們重新設計了 JMeter，增強了它的 GUI和添加了功能測試支持。將來開發(fā)的主要目標是使得 JMeter盡可能地變成一個有用的衰退測試工具，而不損失 JMeter地壓力測試能力 2. Getting Started 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 Web, FTP, JDBC, and JNDI tests. If you want to perform JDBC testing, then you will, of course, need the appropriate JDBC driver from your vendor. JMeter does not e with any JDBC drivers. 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 for JDBC, FTP, and JNDI. Once you are fortable 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. Requirements JMeter requires your puting environment meets some minimum requirements. Java Version JMeter version requires a fully pliant or higher. JMeter and requires a fully pliant or higher. This may seem odd, but we are making a strong effort currently to be patible with the JDK39。t work correctly in this JVM. Operating Systems JMeter has been tested and works under Unix (Solaris, Linux, etc) and Windows (98, NT, 2020, XP). Also works on OpenVMS. JMeter is a 100% Java application and should run correctly on any system that has a pliant Java implementation. Optional If you plan on doing JMeter development or want to use Sun39。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 thirdparty parser in JMeter39。s JavaMail packages and the activation packages to JMeter39。s Java Secure Sockets Extension JSSE). Include the necessary encryption packages in JMeter39。s JDBC driver to the classpath if you want to do JDBC testing. Apache SOAP Apache SOAP requires and . You need to download and copy these two jar files to your jmeter/lib directory. Once the files are in there, JMeter will automatically pick them up. Installation Installing JMeter is a snap. Specifics depend on which release file you downloaded. Downloading the Latest Release We remend 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 JDK correctly installed and the JAVA_HOME environment variable set, there is nothing more for you to do. Downloading Nightly Builds If you do not mind working with betaquality software, then you can download and run the latest nightly build. To install a nightly build, unzip the zip/tar file into the directory where you want JMeter to be installed. Then, open a shell or mand prompt and change to JMeter39。s Classpath JMeter automatically finds classes from jars in its /lib and /lib/ext directories. If you want to add other JAR files to JMeter39。s lib directory. If you have developed new JMeter specific ponents, then you should jar them and copy the jar into JMeter39。一個完整的測試計劃由一個或多個線程組（ Thread Group），邏輯控制器，樣本生成控制器，監(jiān)聽器，定時器（ timer），斷言，和配置元素。另外，元件可以從文件加載并由 “打開 ”選項 添加。 加載和保存元件 要從文件加載元件，在你想要添加所加載的元件的樹元件上右擊，然后選擇 “打開 ”選項。 JMeter將加載元件到樹中。 JMeter將保存選中的元件，和它下面的所有子元件。 隨著 ，測試計劃文件格式變化了。如果你要使用舊的測試計劃，使用 JMeter讀取并以新的格式重新保存它。這些控制器允許你配置某種測試元件的行為。 測試樹本身可以通過拖拽組件來操作。要停止你的測試計劃，從同一個菜單中選擇 “停止 ”。如果JMeter正在運行著，某些監(jiān)聽器可以使這變得顯而易見，但可靠的方法是檢查“運行 ”菜單。 Scoping Rules The JMeter test tree contains elements that are both hierarchical and ordered. Some elements in the test trees are strictly hierarchical (Listeners, Config Elements, PostProcesors, PreProcessors, Assertions, Timers), and some are primarily ordered (controllers, samplers). When you create your test plan, you will create an ordered list of sample request (via Samplers) that represent a set of steps to be executed. These requests are often anized within controllers that are also ordered. Given the following test tree: Example test tree The order of requests will be, One, Two, Three, Four. Some controllers affect the order of their subelements, and you can read about these specific controllers in the ponent reference. Other elements are hierarchical. An Assertion, for instance, is hierarchical in the test tree. If its parent is a request, then it is applied to that request. If its parent is a Controller, then it affects all requests that are descendants of that Controller. In the following test tree: Hierarchy example Assertion 1 is applied only to Request One, while Assertion 2 is applied to Requests Two and Three. Another example, this time using Timers: plex example In this example, the requests are named to reflect the order in which they will be executed. Timer 1 will apply to Requests Two, Three, and Four (notice how order is irrelevant for hierarchical elements). Assertion 1 will apply only to Request Three. Timer 2 will affect all the requests. Hopefully these examples make it clear how configuration (hierarchical) elements are applied. If you imagine each Request being passed up the tree branches, to its parent, then to its parent39。如果選中， JMeter 將會記錄從每個服務器的每個樣本返回的數(shù)據(jù)。如果你在測試是否 JMeter被正確配置和服務器是否返回期望的結果，這是很有用的。如果你在做壓力測試，這個選項