Get desktop application:
View/edit binary Protocol Buffers messages
The bindings of input variables for the test case.
Used in:
A map representing a variable binding where the key is the name of the input variable.
Matches error results from Eval.
Used in:
Success if we match any of these sets.
The input value for a variable binding
Used in:
The type of input value that can be used for a variable binding
A simple literal value for a variable binding
An expression which evaluates to the value of the variable binding. The expression is evaluated using the same runtime environment as the one used for evaluating the expression under test.
A test which should run the given CEL program through parsing, optionally through checking, then evaluation, with the results of the pipeline validated by the given result matcher.
Used in:
Required. The name of the test, which should be unique in the test file.
A description of the test.
Required. The text of the CEL expression.
Disables all macro expansion in parsing.
Disables the check phase.
Disables the evaluate phase.
The type environment to use for the check phase.
The container for name resolution.
The locale to use for the evaluation phase.
Variable bindings to use for the eval phase.
An unspecified result defaults to a matcher for the true boolean value.
A normal value, which must match the evaluation result exactly via value equality semantics. This coincides with proto equality, except for: * maps are order-agnostic. * a floating point NaN should match any NaN.
A result and deduced expression type.
Matches error evaluation results.
Matches one of several error results. (Using explicit message since oneof can't handle repeated.)
Matches unknown evaluation results.
Matches one of several unknown results. (Using explicit message since oneof can't handle repeated.)
The format of a simple test file, expected to be stored in text format. A file is the unit of granularity for selecting conformance tests, so tests of optional features should be segregated into separate files. Deprecated: Use cel.expr.conformance.test.Suite
Required. The name of the file. Should match the filename.
A description of the file.
The contained sections.
A collection of related SimpleTests. The section is the unit of organization within a test file, and should guide where new tests are added.
Used in:
Required. The name of the section.
A description of the section.
The contained tests.
A test to validate a CEL policy or expression. The test case encompasses evaluation of the compiled expression using the provided input bindings and asserting the result against the expected result. It can also validate a raw CEL expression string through parse, check and eval stages, making use of the augmenting CEL environment if provided.
Used in:
Name of the test case.
A description of the test.
The text of the CEL expression.
Serialized environment to be used for compilation and evaluation of the CEL expression for the current test case. This option allows validating the same expression against multiple environments.
Input for the test case
Expected result of the test case.
If specified validates that the deduced type at check time matches If the result kind is not set and this field is set, the test is considered "check-only".
Bypass the type-checking and only attempt to evaluate the parsed expression.
Input for the test case
Used in:
The type of input for the test case
A set of variable bindings to be used for evaluating a checked expression.
A context message represents an input kind in the form of a proto message whose type is defined at runtime.
A context expression representing a context proto variable. The fields of the input proto.Messages are used as top-level variables within an Activation. The expression is evaluated using the cel environment configured for the test suite.
Expected result of the test case.
Used in:
Type of expected result of the test case.
A normal value, which must match the evaluation result exactly via value equality semantics. This coincides with proto equality, except for: * maps are order-agnostic * a floating point NaN should match any NaN
An expression to be evaluated using the cel environment configured for the test suite. The result of this expression must match the result of the test case.
An error evaluation result set. Success if we match all of the errors in the set.
An unknown evaluation result.
A collection of related test cases.
Used in:
Name of the test section.
Description of the test section.
Test cases of the test section. Each test case represents a test scenario.
A test suite is a collection of tests designed to evaluate the correctness of a CEL policy, a CEL expression or the conformance of a CEL implementation to the standard specification.
The name of the test suite.
Description of the test suite.
Test sections of the test suite. Each section represents a behavior to be tested.
Matches a result along with deduced expression type.
Used in:
A normal value, which must match the evaluation result exactly via value equality semantics. This is ignored if the test is `check_only`.
The deduced type of the expression as reported by the checker.
Matches unknown results from Eval.
Used in:
Success if we match any of these sets.