I suggest you use JMeter to create a JMX file and work back from that.
On 02/02/06, John Bullock [EMAIL PROTECTED] wrote:
I am pretty sure it is JMeter. The example that I am working on is a
parameter whose value is a base64-encoded block of text. For example:
property name=Argument.value
I construct my test plans without using the JMeter GUI by directly
constructing .jmx files. I have just discovered that JMeter assumes that the
name and value of each HTTP Argument are URL encoded in the XML file. But I
have the parameters in their raw, un-encoded form. Is there a mode or
I construct my test plans without using the JMeter GUI by directly
constructing .jmx files. I have just discovered that JMeter assumes that the
name and value of each HTTP Argument are URL encoded in the XML file. But I
have the parameters in their raw, un-encoded form. Is there a mode or
On 01/02/06, John Bullock [EMAIL PROTECTED] wrote:
I construct my test plans without using the JMeter GUI by directly
constructing .jmx files. I have just discovered that JMeter assumes that the
name and value of each HTTP Argument are URL encoded in the XML file. But I
have the parameters
I am pretty sure it is JMeter. The example that I am working on is a
parameter whose value is a base64-encoded block of text. For example:
property name=Argument.value
propType=org.apache.jmeter.testelement.property.StringProperty
5 matches
Mail list logo
