You may want to add a results tree listener and take a look at the
request / response. Running the test in the GUI of course.
santiagoloso wrote:
Yeap, I'm passing them. Results for ALL the samples are positive (on the
whole test plan). But the logs on the DB says anonymous instead.
Michael McDonnell wrote:
Are you passing in the username/password variables when you POST the login
form?
On Wed, Apr 8, 2009 at 12:14 PM, santiagoloso
<[email protected]>wrote:
Hi everyone, I'm working on Test Plan for an application that requires
username and password. Due to some permissions thing only some of the
users
loaded on the DB are allowed to use this feature I'll be testing.
Said that, I've configured a CSV file with usernames and passwords (all
allowed to use this feature I'm testing) and setted the thread group to
log
in to the website, and then perform the required steps to get into the
feature and operate over it.
After executing THOUSANDS of times, and checked results, when I ask for
information, the required information is retrieved (analyzed using View
Results in Tree Listener). It's not really important data veracity, so
I'm
not using assertions, just need the performance.
Well, my doubt comes this way: when taking a look at db logs, servers
been
hitted a lot of times, but always by an anonymous user (not by the
usernames
and passwords that are sent within the test plan).
My deduction power tells me that the first steps (those executed before
the
log in) must be anonymous, but, from that step and all that follow,
username
on db logs should be the one inserted on each iteration (csv file brings
multiple username/password combinations, all valid).
Am I wrong? What am I missing?
--
View this message in context:
http://www.nabble.com/Is-this-working-or-not--tp22956547p22956547.html
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]