The following statement returns a boolean value as stated in the product documentation for aqString.StrMatches:result = aqString.StrMatches("dog", "The quick brown fox jumps over the lazy dogs");Value for result is true (as expected).However:var pattern = "dog";var text = "The quick brown fox jumps over the lazy dogs";result = aqString.StrMatches(pattern, text);Value for result is an object??????? Specifically (from the locals window):result (Object) ListSeparator | QuoteSymbol " stAll 3 stLeading 1 stTrailing 2What did I do wrong? I can't believe that this function is designed only to work with hard-coded strings. That would be useless.

Hi David, I tried the following in Test Complete 10, language JScript: function testStrMatches() { var pattern = "dog"; var text = "The quick brown fox jumps over the lazy dogs"; var result = aqString.StrMatches(pattern, text); Log.Message( result ); } This logs True, and inspecting in the debugger shows the value of result = True and the Type = Boolean I guess this doesn't really help, but does show that what you are attempting should work. Regards, Phil Baird

you can use regular expressions to detect patterns....... sub test Call string("The quick brown fox jumps over the lazy dogs",returnValue) end sub function string(obj1,Obj2) Set Expr = New RegExp Expr.Pattern = "dog" Obj2=Expr.test(obj1) End function

Perhaps you could convert the variant values to a string, so you can be sure they are string values in any language.result = aqString.StrMatches(aqConvert.VarToStr(pattern), aqConvert.VarToStr(text));

Phil: I was running in TC 9.31, haven't been able to upgrade to ver 10 yet, looks like it might be time.Murugan: I actually ended up doing something like this. My client wants me to avoid Javascript as much as possible because they need to maintain this testing system after I leave, and the QA team doesn't have programmers. Sometimes it just can't be helped.Paul: I tried what you suggested, but I got the same result as before.Thanks everyone. I think this was a bug in the aqString library that apparently gets fixed in the next release.

Hi David, I still have my old install of Test Complete version 9.31.3889.7 on my machine and tried it with that. The result was the same as with Test Complete 10, the function logs True, and inspecting in the debugger shows the value of result = True and the Type = Boolean I did a quick check and the object you describe is what you get if you inspect the aqString object Phil

aqString.StrMatches only works with hard-coded strings. Seriously???

13 Replies

Philip_Baird
Community Expert
11 years ago

Hi David, I tried the following in Test Complete 10, language JScript:

function testStrMatches() {

var pattern = "dog";

var text = "The quick brown fox jumps over the lazy dogs";

var result = aqString.StrMatches(pattern, text);

Log.Message( result );

}

This logs True, and inspecting in the debugger shows the value of result = True and the Type = Boolean

I guess this doesn't really help, but does show that what you are attempting should work.

Regards,

Phil Baird
murugans1011
Regular Contributor
11 years ago

you can use regular expressions to detect patterns.......

sub test

Call string("The quick brown fox jumps over the lazy dogs",returnValue)

end sub

function string(obj1,Obj2)

   Set Expr = New RegExp

   Expr.Pattern = "dog"

   Obj2=Expr.test(obj1)

End function
paul_scroce
Frequent Contributor
11 years ago
Perhaps you could convert the variant values to a string, so you can be sure they are string values in any language.

result = aqString.StrMatches(aqConvert.VarToStr(pattern), aqConvert.VarToStr(text));
dpeterson
Occasional Contributor
11 years ago
Phil: I was running in TC 9.31, haven't been able to upgrade to ver 10 yet, looks like it might be time.

Murugan: I actually ended up doing something like this. My client wants me to avoid Javascript as much as possible because they need to maintain this testing system after I leave, and the QA team doesn't have programmers. Sometimes it just can't be helped.

Paul: I tried what you suggested, but I got the same result as before.

Thanks everyone. I think this was a bug in the aqString library that apparently gets fixed in the next release.
Philip_Baird
Community Expert
11 years ago

Hi David, I still have my old install of Test Complete version 9.31.3889.7 on my machine and tried it with that.

The result was the same as with Test Complete 10, the function logs True, and inspecting in the debugger shows the value of result = True and the Type = Boolean

I did a quick check and the object you describe is what you get if you inspect the aqString object

Phil
dpeterson
Occasional Contributor
11 years ago
Well, crud! That is bad news indeed... So what the heck went wrong in my world?
Philip_Baird
Community Expert
11 years ago

Hi David, I do not know, would it be possible to post the complete function code in which the issue occurs?

This may provide a few clues.

Phil
dpeterson
Occasional Contributor
11 years ago
I'm afraid I can't do that due to licensing, copyright and other reasons. I guess I'll just have to punt.
Philip_Baird
Community Expert
11 years ago

Ok, just as a matter of interest, could you try copying the function in my original post, testStrMatches(), into Test Complete and running it, just to see if it works?

Phil
dpeterson
Occasional Contributor
11 years ago
I'll try it and let you know. Thanks for your help.