May I suggest someone create a Bugzilla report, with enough details to be able to reproduce the problem easily?
S. >-----Original Message----- >From: Sergey Almyashev [mailto:[EMAIL PROTECTED] >Sent: 19 February 2004 07:05 >To: JMeter Users List >Subject: RE: wiki page - parameterize tests > > >I've met such a problem too. Something wrong with >multipart/form-data mime-type. E.g. when I used form without >binaries and wanted to pass my form data as >multipart/form-data, Jmeter ignored my header "contentType" >and place the header "ContentType: >application/x-www-urlencoded". Testing of our application failed. > >> -----Original Message----- >> From: Mark Lybarger [mailto:[EMAIL PROTECTED] >> Sent: Thursday, February 19, 2004 5:26 AM >> To: JMeter Users List >> Subject: Re: wiki page - parameterize tests >> >> >> I'll definately take a look at these and perhaps see about >> using the wiki. >> >> In the Component reference, the Http Request section, maybe >some more >> could be added to the mime type. I had a form which was >> multipart and >> the parameters weren't coming through b/c i didn't set the recording >> (actually, i used the proxy to originally grab the page, and >> _it_ didn't >> pick up that the form enctype was multipart/form-data. >> Though even if >> it were in the doc, i probably would have missed it. >> >> Using the proxy to grab all your form data and requests, etc is VERY >> nice to save some work, but you still have to realize that >> you have to >> tweak the tests a bit. >> >> Mark Lassau wrote: >> >> > Mark Lybarger wrote: >> > >> >> i'm fairly new to JMeter. >> >> >> >> on the wiki, >> http://nagoya.apache.org/wiki/apachewiki.cgi?JMeterFAQ, >> >> under /How do I parameterize my JMeter test cases?, /item >> 2 says to >> >> "Click the Add button to add the following user defined >> variables to >> >> the Test Plan node:". i think that should read: >> >> "Click the Add button to add a Pre Processor > User >> Parameter to the >> >> Test Plan node. Click Add Variable to add the folowing >> >> variables/values to the User Parameter list. >> >> >> >> i'm also extremely interested in the section that follows, the >> >> dynamic parameters. unfortunately, being a java junkie, i >> don't have >> >> much experience with perl regular expressions. is there >perhaps a >> >> collection of usage of these regular expressions with >JMeter? one >> >> thing that i can think of is, say you have a hidden input form >> >> element that contains a value that you need to grab: >> >> >> >> <input type="hidden" name="HiddenVarYouCantSee" >> >> value="IChangePerRequest" /> >> >> <input type="hidden" name="SecondHidden" >> value="IChangePerRequest" /> >> >> <input type="hidden" name="ThirdHidden" >> value="IChangePerRequest" /> >> >> >> >> >> >> how would i grab the value(s) here? yes, there's other hidden >> >> variables on the form that i don't care about. i only >> know the name >> >> of the ones that i do care about. >> >> >> >> thanks! >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: >> [EMAIL PROTECTED] >> >> >> >> >> > Send this value with your request (and so on...) >> > ${__regexFunction(<input type="hidden" name="HiddenVarYouCantSee" >> > value="(.*)" />,$1$,1,,,)} >> > >> > I'd suggest you read through the whole user manual >> > http://jakarta.apache.org/jmeter/usermanual/index.html >> > before using JMeter. >> > Glance over the stuff you think you aren't interested in. >> > Some of the info you want is not necessarily were you would >> first look. >> > >> > I found chapter 13 >> > >> <http://jakarta.apache.org/jmeter/usermanual/component_referen >ce.html>, >> "Component Reference", the most useful, although at first glance you >> would think it is a reference to look up one at a time later. >> >> see >> http://jakarta.apache.org/jmeter/usermanual/component_reference.html#__regex Function > > to figure out the regex voodoo above. > > > > --------------------------------------------------------------------- > 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] ___________________________________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ___________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
