What is the bug?
it seems that various tests still only test against the old evaluator. e.g. DlsTermLookupQueryTest uses the old evaluator, evaluator.
i didn't check other tests; somebody should check all tests and make sure that they cover all evaluators (and other possible variations).
How can one reproduce the bug?
n/a
What is the expected behavior?
all functional tests run against all evaluator versions which are implemented (where applicable; if tests only work with certain versions they should be annotated accordingly).
What is your host/environment?
n/a
Do you have any screenshots?
n/a
Do you have any additional context?
in #6244 i've fixed this for DlsTermLookupQueryTest since i needed it (my test for the new feature was passing but the actual use-case in a running cluster still failed - because the test used the old evaluator while the running cluster used the new).
What is the bug?
it seems that various tests still only test against the old evaluator. e.g.
DlsTermLookupQueryTestuses the old evaluator, evaluator.i didn't check other tests; somebody should check all tests and make sure that they cover all evaluators (and other possible variations).
How can one reproduce the bug?
n/a
What is the expected behavior?
all functional tests run against all evaluator versions which are implemented (where applicable; if tests only work with certain versions they should be annotated accordingly).
What is your host/environment?
n/a
Do you have any screenshots?
n/a
Do you have any additional context?
in #6244 i've fixed this for
DlsTermLookupQueryTestsince i needed it (my test for the new feature was passing but the actual use-case in a running cluster still failed - because the test used the old evaluator while the running cluster used the new).