Hi Justin,
I have tried a couple of variations of this but haven’t found the
answer.
Can you please send me your test scenario file so that I can see
exactly see what you did? Thanx! This enables me to help you further.
I am attaching an error log.
The attached error log tells that ULC Load "found non perfect
matches". This indicates that the response for the replayed ULC
sampler does not correlate to the recorded one. At the end of the
error log you can find the content of the replayed ULC sampler
("played round trip"). It tells that your application responds with a
"You have entered an invalid Username or Password." error message. At
that point ULC Load cannot continue and stops the load test.
Navis works with an ULC Load evaluation licenses since August 2008 (=>
since 5 months!). From what I understood, Navis successfully evaluated
ULC Load, i.e. was able to do a load test for their ULC based
application.
Can you please give me some more information about your plans with ULC
Load?
Regards Dany
On 17.01.2009, at 00:41, Hughes, Justin wrote:
Dear Canoo,
I sent this email two days ago, got a response about how I had sent
it to the wrong email address, resent it to the correct one, and
then receive a response that doesn’t even address my problem. It
sounds like you had my question confused with someone else’s. Please
review below and let me know your thoughts.
I am using an evaluation license of ULC load 3.0.2 to load test my
company’s product. I am having trouble parameterizing the usernames
and passwords to create 5 different logins. I am following the User
Guide’s steps but receive login errors each time.
My steps:
1. I add the User Parameters to the existing Thread group
2. I add a variable with 5 different user names to the User
Parameters
3. The password is the same for all so I first tried adding
another variable called password and imputing the same value for
each, but that gave me login errors. Then I tried putting the
password variable in the Test Plan node (User Defined Variables)
because that gave the variable only one value which is what I want,
but got login errors also.
4. I then went in to add 2 Method Modifiers, one for the
username and one for the password. I changed only the New argument
value which I put as ${username} and ${password} respectively.
5. I increased the number of threads to 5. Then Run it. I have
always gotten login errors doing this method.
I have tried a couple of variations of this but haven’t found the
answer.
I did get it to work, but I had to omit the User Parameter node
altogether. I simply added in 4 ULC Modifiers under the login ULC
Sampler, each with the Old Argument as my original username, and the
New Argument as TEST0001, TEST0002. TEST0003…etc for each method
modifier.
This worked but is convoluted and clearly is not the proper method.
Can you suggest any alternatives or any steps I might be missing?
I am attaching an error log.
Thank you ,
Justin Hughes
<ULC Error.docx>
