[Apache JMeter Wiki] Updated: UserManual/Elements

[ja...@apache.org]

   Date: 2005-03-07T08:48:10
   Editor: MichaelStover
   Wiki: Apache JMeter Wiki
   Page: UserManual/Elements
   URL: http://wiki.apache.org/jakarta-jmeter/UserManual/Elements

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -18,7 +18,7 @@
 
 By default, a thread group is configured to loop indefinitely through its elements. Alternatively, you can set the number of times the thread group will loop before ending. If the number is set at one, then JMeter will execute the test only once before stopping.
 
-  Version 1.9 introduces a test run '''scheduler'''. Click the checkbox at the bottom of the Thread Group panel to reveal two extra fields in which you can enter the start and end times of the run. When the test is started, JMeter will wait if necessary until the start-time has been reached. At the end of each cycle, JMeter checks if the end-time has been reached, and if so, the run is stopped, otherwise the test is allowed to continue until the iteration limit is reached.
+Version 1.9 introduces a test run '''scheduler'''. Click the checkbox at the bottom of the Thread Group panel to reveal two extra fields in which you can enter the start and end times of the run. When the test is started, JMeter will wait if necessary until the start-time has been reached. At the end of each cycle, JMeter checks if the end-time has been reached, and if so, the run is stopped, otherwise the test is allowed to continue until the iteration limit is reached.
 [[Anchor(controllers)]]
 == Controllers ==
 
@@ -27,18 +27,18 @@
 To understand the effect of Controllers on a test plan, consider the following test tree:
 
  * Test Plan
-  1. Thread Group
-   a. Once Only Controller
-    i.Login Request (an HTTP Request )
-   a. Load Search Page (HTTP Sampler)
-   a. Interleave Controller
-    i. Search "A" (HTTP Sampler)
-    i. Search "B" (HTTP Sampler)
-    i. HTTP default request (Configuration Element)
-   a. HTTP default request (Configuration Element)
-   a. Cookie Manager (Configuration Element)
+  A. Thread Group
+   1. Once Only Controller
+    a.Login Request (an HTTP Request )
+   1. Load Search Page (HTTP Sampler)
+   1. Interleave Controller
+    a. Search "A" (HTTP Sampler)
+    a. Search "B" (HTTP Sampler)
+    a. HTTP default request (Configuration Element)
+   1. HTTP default request (Configuration Element)
+   1. Cookie Manager (Configuration Element)
 
-The first thing about this test is that the login request will be executed only the first time through. Subsequent iterations will skip it. This is due to the effects of the Once Only Controller .
+The first thing about this test is that the login request will be executed only the first time through. Subsequent iterations will skip it. This is due to the effects of the Once Only Controller.
 
 After the login, the next Sampler loads the search page (imagine a web application where the user logs in, and then goes to a search page to do a search). This is just a simple request, not filtered through any Controller.
 
@@ -62,7 +62,7 @@
  * Java object request
  * LDAP Request
  * SOAP/XML-RPC Request
- * WebService (SOAP) Request (Alpha Code)
+ * [:../Reference/WebServiceRequest: WebService (SOAP) Request (Alpha Code)]
 
 Each sampler has several properties you can set. You can further customize a sampler by adding one or more Configuration Elements to it. Also, note that JMeter sends requests in the order that you add them to the tree.
 
@@ -72,7 +72,7 @@
 
 If you are interested in having JMeter perform basic validation on the response of your request, add an Assertion to the Request controller. For example, in stress testing a web application, the server may return a successful "HTTP Response" code, but the page may have errors on it or may be missing sections. You could add assertions to check for certain HTML tags, common error strings, and so on. JMeter lets you create these assertions using regular expressions.
 
-[wiki:Self:UserManual/reference#samplers JMeter's built-in samplers]
+[wiki:Self:UserManual/Reference#samplers JMeter's built-in samplers]
 [[Anchor(listeners)]]       
 == Listeners ==
 
@@ -82,7 +82,7 @@
 
 Listeners can be added anywhere in the test. They will collect data only from elements at or below their level.
 
-There are several interesting [wiki:Self:UserManual/reference#listeners listeners] that come with JMeter.
+There are several interesting [wiki:Self:UserManual/Reference#listeners listeners] that come with JMeter.
 [[Anchor(timers)]]
 == Timers ==
 
@@ -111,7 +111,7 @@
 Also, a configuration element inside a tree branch has higher precedence than the same element in a "parent" branch. For example, we defined two HTTP Request Defaults elements, "Web Defaults 1" and "Web Defaults 2". Since we placed "Web Defaults 1" inside a Loop Controller, only "Web Page 2" can access it. The other HTTP requests will use "Web Defaults 2", since we placed it in the Thread Group (the "parent" of all other branches).
 
  http://jakarta.apache.org/jmeter/images/screenshots/http-config/http-config-example.png [[BR]]
- Figure 1 - Test Plan Showing Accessability of Configuration Elements
+ ~-Figure 1 - Test Plan Showing Accessability of Configuration Elements-~
 [[Anchor(preprocessors)]]
 == Pre-Processor Elements ==
 

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org