It's working now..it was the regular expression that threw it off. Thank you all.
On Mon, Jan 2, 2012 at 10:29 PM, Robin D. Wilson <[email protected]> wrote: > I think your Template needs to be: $1$ > > Also, your regex could be a little more flexible: > > name[^"]*"responseSize"[^"]*value[^"]*"([^"]*)" > > This prevents other things in the <input...> from throwing off your regex. > (I've found that when I setup a test case, if I try to make my regular > expressions very flexible, they still work pretty reliably when my code > changes slightly.) > > Basically, the above regex assumes that you will have a 'name', followed by > "responseSize" (with the " quotes around it) followed by 'value', with > anything except ", followed by ", followed by the value you want up to the > next "... If you don't put the '>' on the end, then if your code changes to > add some more attributes to the <input ...> your regex will still work (for > example, what if the code changed the input to end with '/>' instead of '>' > - your original regex would stop working, but the more flexible one above > would still work fine). Also, if you don't start your regex with '<input', > your code could add some more attributes _before_ the pattern you are > looking to extract, and the regex will still work for the pattern (for > example, the code might add an 'id="mystyle"', or 'class="inputClass"' > which > would break your original regex, but not the one above). > > Lastly, for me - the easiest way to test this stuff is to add a 'tree' > listener, capture the page that you are trying to extract with the regex, > and paste the entire page into a regex tool (such as: > http://gskinner.com/RegExr/ or http://regexpal.com/ ). Then paste your > regex pattern into the regex field of the tool, and see what it highlights > (it should highlight the entire regex pattern if the regex is correct). I > find that when my regex patterns don't work - cutting them down to the most > basic pattern and then building them back up to what I need works the best. > > There are a couple of risks with very 'flexible' patterns - most > significantly, that the pattern will match more than 1 place in your HTTP > response - so be careful about what you setup as your minimum level of > flexibility. > > -- > Robin D. Wilson > Sr. Director of Web Development > KingsIsle Entertainment, Inc. > VOICE: 512-777-1861 > www.KingsIsle.com > > -----Original Message----- > From: Annie L [mailto:[email protected]] > Sent: Monday, January 02, 2012 9:38 PM > To: JMeter Users List > Subject: Re: http request...passing data set from one http request to > another. > > I tried Regular Expression Extractor but it doesn't seem to pick up the > value.. > In my HTML response, there is a string like this > > <input type = "text" name = "responseSize" value = "5"> > > I want to capture the responseSize value (5)... > > Reference Name: responseSize > Regular Expression: <input type = "text" name = "responseSize" value = > "(.+?)"> > Template: $1# > Match No. (0 for Random): 1 > Default Value: 0 > > I then created an If Controller based on "responseSize": > '${responseSize}'!='0' to do a subsequent http request. > > It never goes into my 2nd http request. Is my expression for responseSize > variable correct? > > Thanks, > -A > > > > > > On Mon, Jan 2, 2012 at 11:08 AM, Flavio Cysne <[email protected]> > wrote: > > > Annie, > > > > add a Regular Expression Extractor to set a variable value with > > this data set, and use it as a request parameter value onto the next > > http request. > > > > Hope it helps you. > > Flávio Cysne > > > > 2012/1/2 Annie L <[email protected]> > > > > > > Hi all, > > > > I have a http request that would give me a data set which I need > > > > to be able to pass that onto the next http request. I can't > > > > figure out how > > to > > > do > > > > it in jmeter. Anyone has any idea? > > > > Thank you, > > > > Annie > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
