graphql-engine/v3/crates/metadata-resolve/tests/failing
Daniel Chambers 962ae79e99 Move AggregateExpression resolve tests from engine tests to metadata-resolve tests (#714)
## Description
This PR moves all the tests that were added to
`crates/engine/tests/validate_metadata_artifacts/aggregate_expressions`
to the metadata-resolve `metadata_golden_tests`.

All the `error.txt` files got renamed to `expected_error.txt` and the
`metadata is not consistent:` bit on the front of the error got trimmed
off.

I had to change the way that `test_failing_metadata` works so that
instead of looking for directories under `failing/` it looks for
`metadata.json` files under `failing/`. This is because not every
directory has a test in it, some directories are just used for grouping
(eg `failing/aggregate_expressions/`). This doesn't change what tests
get run. The only side effect is that every test name has `_metadata`
suffixed to it (the filename). 😢 `test-each` doesn't appear to offer a
way to disable this behaviour.

V3_GIT_ORIGIN_REV_ID: dece7cd3bb4623c51050d12471d2c0990fd69bfd
2024-06-13 08:20:21 +00:00
..
aggregate_expressions Move AggregateExpression resolve tests from engine tests to metadata-resolve tests (#714) 2024-06-13 08:20:21 +00:00
boolean_expression Allow nested metadata-resolve tests (#697) 2024-06-11 14:11:10 +00:00
command_no_ndc_function Allow nested metadata-resolve tests (#697) 2024-06-11 14:11:10 +00:00
simple Allow nested metadata-resolve tests (#697) 2024-06-11 14:11:10 +00:00
subgraph_invalid_name Allow nested metadata-resolve tests (#697) 2024-06-11 14:11:10 +00:00
supergraph_too_many_graphql_configs Allow nested metadata-resolve tests (#697) 2024-06-11 14:11:10 +00:00