bug?: Regexp and case sensitive

[Smersh]

That made me puzzled...

If set 'case sensitive' option in regular expression test shows the opposite result, as if above option is set to off. And vice versa.

I add expression .*loopback.* [Resualt is FALSE] to regexp "Network interfaces for discovery", test it, and don't understand why items with "Loopback interface" appears on hosts

[steveboyson]

Which version?

And I would suggest to use "^(loopback)$" as regexp.

[Smersh]

Version 2.2.2

Does not ^ mean beginning and $ ending of string? But Interface name is "MS TCP Loopback Interface" or something like that.
Even so, the problem is not in the expression, but in "case sensitive" option.

A specific example:

Expression: ^(one|two|three)$
Expression type: Result is TRUE
Case sensitive: YES
a)  Test string: two
     Combined result: TRUE
b)  Test string: tWo
     Combined result: TRUE

And vise versa:

Expression: ^(one|two|three)$
Expression type: Result is TRUE
Case sensitive: NO
a)  Test string: two
     Combined result: TRUE
b)  Test string: tWo
     Combined result: FALSE

P.S. After all, it's not too annoying. Just bring to the attention.

P.P.S. Gone to learn English...

[simon123]

I can confirm this behavior on our 2.2.2 platform.
The checkbox does the exact opposite of the description next to it.
So you need to check "Case Sensitive" to yes to get it to ignore the case type, which would actually make it "Case Insensitive"...