qileilove

There are two ways to create test cases for testing an LDAP Server.

1. Inbuilt Test cases.
2. User defined Test cases.

There are four test scenarios of testing LDAP. The tests are given below:

1. Add Test
1. Inbuilt test :

   This will add a pre-defined entry in the LDAP Server and calculate the execution time. After execution of the test, the created entry will be deleted from the LDAP Server.

2. User defined test :

   This will add the entry in the LDAP Server. User has to enter all the attributes in the table.The entries are collected from the table to add. The execution time is calculated. The created entry will not be deleted after the test.

2. Modify Test
1. Inbuilt test :

   This will create a pre-defined entry first, then will modify the created entry in the LDAP Server.And calculate the execution time. After execution of the test, the created entry will be deleted from the LDAP Server.

2. User defined test

   This will modify the entry in the LDAP Server. User has to enter all the attributes in the table. The entries are collected from the table to modify. The execution time is calculated. The entry will not be deleted from the LDAP Server.

3. Search Test
1. Inbuilt test :

   This will create the entry first, then will search if the attributes are available. It calculates the execution time of the search query. At the end of the execution,created entry will be deleted from the LDAP Server.

2. User defined test

   This will search the user defined entry(Search filter) in the Search base (again, defined by the user). The entries should be available in the LDAP Server. The execution time is calculated.

4. Delete Test
1. Inbuilt test :

   This will create a pre-defined entry first, then it will be deleted from the LDAP Server. The execution time is calculated.

2. User defined test

   This will delete the user-defined entry in the LDAP Server. The entries should be available in the LDAP Server. The execution time is calculated.
   有两种方法可以创建测试用例测试LDAP服务器。
   内置的测试用例。
   用户定义的测试用例。
   有四个测试场景的测试LDAP。给出了测试如下:
   添加测试
   内置的测试:
   这将添加一个预定义的条目在LDAP服务器和计算执行时间。执行测试后,创建的条目将被删除从LDAP服务器。
   用户定义的测试:
   这将在LDAP服务器中添加条目。用户必须输入表中所有的属性。从表中收集到的条目添加计算执行时间。创建的条目测试后将不会被删除。
   修改测试
   内置的测试:
   这将创建一个预定义的条目,然后将修改在LDAP服务器创建的条目。并计算执行时间。执行测试后,创建的条目将被删除从LDAP服务器。
   用户定义的测试
   这将修改LDAP服务器中的条目。用户必须输入表中所有的属性。从表中收集修改的条目。计算执行时间。条目不会从LDAP服务器中删除。
   搜索测试
   内置的测试:
   这将创建的条目,然后将搜索可用的属性。它计算搜索查询的执行时间。结束时执行,创建条目将被删除从LDAP服务器。
   用户定义的测试
   这将搜索用户定义的条目(搜索过滤器)在搜索基地(再一次,由用户定义的)。应该在LDAP服务器中可用的条目。计算执行时间。
   删除测试
   内置的测试:
   这将创建一个预定义的条目,然后它将从LDAP服务器中删除。计算执行时间。
   用户定义的测试
   这将删除用户定义的条目在LDAP服务器。应该在LDAP服务器中可用的条目。计算执行时间。

Parameters

Control Panel Parameters Attribute Description Required Name Descriptive name for this element that is shown in the tree. Yes Variable Name The name of the variable in which to store the random string. Yes Format String The java.text.DecimalFormat format string to be used. For example "000" which will generate numbers with at least 3 digits, or "USER_000" which will generate output of the form USER_nnn. If not specified, the default is to generate the number using Long.toString() No Minimum Value The minimum value (long) of the generated random number. Yes Maximum Value The maximum value (long) of the generated random number. Yes Random Seed The seed for the random number generator. Default is the current time in milliseconds. If you use the same seed value with Per Thread set to true, you will get the same value for earch Thread as per Random class. No Per Thread(User)? If False, the generator is shared between all threads in the thread group. If True, then each thread has its own random generator. Yes

18.4.13 TCP Sampler Config

The TCP Sampler Config provides default data for the TCP Sampler Control Panel Parameters Attribute Description Required Name Descriptive name for this element that is shown in the tree. No TCPClient classname Name of the TCPClient class. Defaults to the property tcp.handler, failing that TCPClientImpl. No ServerName or IP Name or IP of TCP server No Port Number Port to be used No Re-use connection If selected, the connection is kept open. Otherwise it is closed when the data has been read. Yes Close connection If selected, the connection will be closed after running the sampler. Yes SO_LINGER Enable/disable SO_LINGER with the specified linger time in seconds when a socket is created. If you set "SO_LINGER" value as 0, you may prevent large numbers of sockets sitting around with a TIME_WAIT status. No End of line(EOL) byte value Byte value for end of line, set this to a value outside the range -128 to +127 to skip eol checking. You may set this in jmeter.properties file as well with eolByte property. If you set this in TCP Sampler Config and in jmeter.properties file at the same time, the setting value in the TCP Sampler Config will be used. No Connect Timeout Connect Timeout (milliseconds, 0 disables). No Response Timeout Response Timeout (milliseconds, 0 disables). No Set Nodelay Should the nodelay property be set? No Text to Send Text to be sent

Control Panel   If you have more than one Thread Group, make sure you use different names for different values, as UDVs are shared between Thread Groups. Also, the variables are not available for use until after the element has been processed, so you cannot reference variables that are defined in the same element. You can reference variables defined in earlier UDVs or on the Test Plan.   Parameters Attribute Description Required Name Descriptive name for this element that is shown in the tree. No User Defined Variables Variable name/value pairs. The string under the "Name" column is what you'll need to place inside the brackets in ${...} constructs to use the variables later on. The whole ${...} will then be replaced by the string in the "Value" column. No

18.4.10 Login Config Element

The Login Config Element lets you add or override username and password settings in samplers that use username and password as part of their setup. Control Panel Parameters Attribute Description Required Name Descriptive name for this element that is shown in the tree. No Username The default username to use. No Password The default password to use. (N.B. this is stored unencrypted in the test plan) No

18.4.17 Simple Config Element

The Simple Config Element lets you add or override arbitrary values in samplers. You can choose the name of the value and the value itself. Although some adventurous users might find a use for this element, it's here primarily for developers as a basic GUI that they can use while developing new JMeter components. Control Panel Parameters Attribute Description Required Name Descriptive name for this element that is shown in the tree. Yes Parameter Name The name of each parameter. These values are internal to JMeter's workings and are not generally documented. Only those familiar with the code will know these values. Yes Parameter Value The value to apply to that parameter.

18.4.16 Counter

Allows the user to create a counter that can be referenced anywhere in the Thread Group. The counter config lets the user configure a starting point, a maximum, and the increment. The counter will loop from the start to the max, and then start over with the start, continuing on like that until the test is ended. From version 2.1.2, the counter now uses a long to store the value, so the range is from -2^63 to 2^63-1. Control Panel Parameters Attribute Description Required Name Descriptive name for this element that is shown in the tree. No Start The starting number for the counter. The counter will equal this number during the first iteration. Yes Increment How much to increment the counter by after each iteration. Yes Maximum If the counter exceeds the maximum, then it is reset to the Start value. For versions after 2.2 the default is Long.MAX_VALUE (previously it was 0). No Format Optional format, e.g. 000 will format as 001, 002 etc. This is passed to DecimalFormat, so any valid formats can be used. If there is a problem interpreting the format, then it is ignored. [The default format is generated using Long.toString()] No Reference Name This controls how you refer to this value in other elements. Syntax is as in user-defined values : $(reference_name} . Yes Track Counter Independently for each User In other words, is this a global counter, or does each user get their own counter? If unchecked, the counter is global (ie, user #1 will get value "1", and user #2 will get value "2" on the first iteration). If checked, each user has an independent counter. No Reset counter on each Thread Group Iteration This option is only available when counter is tracked per User, if checked, counter will be reset to Start value on each Thread Group iteration. This can be useful when Counter is inside a Loop Controller. No