You can also omit the .* - they don't do anthing useful in this context.
GetPayment => look for GetPayment GetPayment.* => look for GetPayment follow by zero or more characters which has the same effect, but will take longer to process. A trailing (or leading) .* is rarely needed, and certainly not here. On 01/12/06, Ivan Rancati <[EMAIL PROTECTED]> wrote:
hi Francesco, I think that the regular expression parser needs the expression in square brackets. Also, I think that * should be .* if you want "any number of characters" Can you try with [GetPayment.*|Workflow.*] I find this site useful as a regex reference http://www.regular-expressions.info/ Francesco.Croci wrote: > > > - I also attached a "Response Assertion" with "Text Response" and > "Contains" selected and "GetPayment* | Workflow*" as "patterns to test". > > The response I get back is: > > ?xml version="1.0" > encoding="utf-8"?>GetPaymentMethodtruetruetruetruetrue00 > > so I would suppose the assertion is true, but under the Assertion Result > listener stays > > "StartCheckout > Test failed, text expected to contain /(GetPayment* | Work*)/" > > If I put only "GetPayment*" as pattern to test, then I get a positive > match... > > Do I make something wrong? How do you build then "OR" clauses? > > -- View this message in context: http://www.nabble.com/-newbie--A-couple-of-questions-tf2736841.html#a7636403 Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
