Nah, it's fine. Without your suggestion, I could not understand where to
start :-)

Cheers!

Le 05/06/2015 15:56, Bob Nance a écrit :
> Sorry for pushing you down the wrong path. 
> 
> ---
>  Bob Nance
>  Novation Systems
>  256-534-4620
>  
> (iPhone-flavored)
> 
> 
>> On Jun 5, 2015, at 8:46 AM, Vincent Lequertier <[email protected]> wrote:
>>
>> Right, the regex was unnecessary. Only using the response assertion for now. 
>> That's cleaner :-)
>>
>> Thanks
>>
>> ---
>> Vincent Lequertier
>> [email protected]
>>
>> Le 2015-06-05 15:26, Robin D. Wilson a écrit :
>>> Actually, you should only need the Response Assertion, the regular
>>> expression extractor would be necessary only if you needed to use the
>>> variable later in the test script.
>>> Keep in mind, adding 'parsers' to responses increases the amount of
>>> effort JMeter has to put into running the test - slowing JMeter down.
>>> While it is certainly necessary to have some of these elements in your
>>> test plan, it is best to keep them to the minimum necessary to
>>> complete the objective.
>>> --
>>> Robin D. Wilson
>>> Sr. Director of Web/Java Engineering
>>> KingsIsle Entertainment, Inc.
>>> VOICE: 512-777-1861
>>> www.KingsIsle.com
>>> -----Original Message-----
>>> From: Vincent Lequertier [mailto:[email protected]]
>>> Sent: Friday, June 05, 2015 8:19 AM
>>> To: JMeter Users List
>>> Subject: Re: Login test always returns success
>>> Got it to work through regular expression extractor and variable-based
>>> response assertion. Thank you for the pointer :-)
>>> ---
>>> Vincent Lequertier
>>> [email protected]
>>> Le 2015-06-05 14:48, Bob Nance a écrit :
>>>> Use a regular expression extractor to look for that string and act on
>>>> it. Fail the test if you get that string.
>>>> ---
>>>> Bob Nance
>>>> Novation Systems
>>>> 256-534-4620
>>>> (iPhone-flavored)
>>>>> On Jun 5, 2015, at 7:37 AM, Vincent Lequertier <[email protected]> wrote:
>>>>> Hi,
>>>>> I'm building a test plan to test login on a web app. I'm using an
>>>>> HTTP request with the POST method. If the credentials are incorrect,
>>>>> the website is returning an alert() in javascript, like this:
>>>>> <script language="JavaScript">
>>>>>   alert('le code utilisateur et/ou le mot de passe sont
>>>>> incorrects'); </script>
>>>>> And the URL returned looks like this: xxxxx/login.do?login_error=1
>>>>> Actually, although the login fails, the test returns success because
>>>>> IMHO jmeter does not take care of that. How can I make jmeter analyse
>>>>> the response from the request so it can grab the javascript code
>>>>> and/or URL and then indicates the error? As I'm new to the jmeter
>>>>> world, can someone provide me a step by step to do this?
>>>>> Let me know if you need more infos. Thanks in advance for any help.
>>>>> --
>>>>> Vincent Lequertier
>>>>> ---------------------------------------------------------------------
>>>>> 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]
>>> ---------------------------------------------------------------------
>>> 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]
>>
>> ---------------------------------------------------------------------
>> 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]
> 
> 

-- 
Vincent Lequertier
[email protected]
wwww.vincentlequertier.tk

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to