Tester

This transformer accepts any feature.

If the test(s) pass, the feature is output via the Passed port.

If the test(s) fail, the feature is output via the Failed port.

The Pass Criteria defines how multiple clauses are interpreted in the final classification of the incoming feature. The possible choices are: All Tests (AND), One Test (OR), and Composite Test.

Here are descriptions of the three choices, and relevant scenarios.

The expression to be used when the Pass Criteria parameter is Composite Test. The expression can refer to a clause from the Test Clauses table using that clause's row number.

Values

The Value columns (operands) may be a literal constant, the value of an attribute, a published parameter or a calculated value that is a combination of the above. If it is a calculated function, the function will be executed on the current feature and the result will be used for the test.

Operators

The Operator column is one of: =, !=, <, >, <=, >=, In, In range, Like, Matches Regex, Contains, Begins With, Ends With, Type is, and Encodable in.

Some operators, such as = and !=, have conventional behavior except as documented here. When the comparison operators =, !=, <, >, <=, >= are applied to null, missing, and empty string values, the trio will all evaluate to the empty string. Thus, they are pairwise equal in the context of these comparison operators. Further, the following comparison ordering is respected:

Null, missing, empty string < numbers < other values

Other, less conventional operators are described in more detail here:

If you choose one of the operators: Attribute Is Empty String, Attribute Is Null, or Attribute Is Missing, the Left Value will be considered an attribute name regardless of the icon shown. To force the Tester to use the value of an attribute, attrName, as the attribute name, you must explicitly type @Value(attrName) into the Left Value field.

String ranges (i.e. a-d) can also be specified. If you want to test for values that contain a hyphen, those values should be enclosed in quotation marks. For example, if x=LL-27, then x In "LL-27","LL-83" would be true. On the other hand, x In LL-27,LL-83 would be false. This is because LL-27 and LL-83 are treated as two empty string ranges, since numbers are ordered earlier than letters when considered as strings.

Negate

A checkbox indicating that the test should return the false if the “<lhs> <op> <rhs>” expression is true and vice versa.

For example,

X=abcd, is 'abcde' Contains X if negated (answer no = Failed)

X=5, Y=1,2,3,4 is X In Y if negated (answer yes = Passed)

Mode

When Mode is set to Automatic or Numeric, the Tester will compare operands as numbers if possible, and as strings otherwise.

When Mode is set to String, the Tester will compare operands as strings, and will not attempt numeric conversions.

Let us refer to strings that can be interpreted as numbers, such as "4E5", as alphanumeric strings. For an alphanumeric string, if you set Mode to Automatic or Numeric, it will be treated as a number if the other operand is also an alphanumeric string, and furthermore the operator used is available in Numeric mode.

For example, if Mode is set to Automatic or Numeric, “4E5=400000” will pass the test. If, on the other hand, you want “4E5=400000” to fail the test, set Mode to String.