It looks as though the SampleResult fields are not being utilised fully by the LDAP code.
It seems to me that the response code could be used to distinguish various kinds of success - for example, using HTTP-style values: 2xx - search succeeded, some results found 2yy - search succeeded, no results found 4xx - some kind of error 5xx - another kind of error I leave it to others more familiar with LDAP as to what exact form the error codes should take (and what the corresponding messages should be), but I think this approach would fit in with the rest of JMeter, and would allow the use of a Response Assertion to convert a search with no results into a failed sample. == The other area where the sample result could be better used is the response Data. This is currently set to "success full" - but does not appear in the Tree View, because the DataType is not being set to TEXT. The sampler could have another field to specify which attributes to return. [Is there a sensible default set of attributes that applies to all/most LDAP implementations? I don't know.] == If these suggestions make sense, I am happy to help with updating the code in CVS. -- Sebastian Bazley --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
