I wonder how useful this test is? Seems an awful lot like achange-detector test to me. I'd be fine adding the constant without adding the test.

Alternatively, maybe there's a system test we could write to make sure this is synced with thebigquery discovery document? But even then, compression isn't a true enum. The allowed values are only listed in the documentation string from what I can tell.

@tswast

I will remove this test.

In terms of attempting to ensure that this matches the discovery docs... the terms referenced by the docs are present in the description, as you note, so we would need some mechanism to extract them from the discovery doc, which feels somewhat fragile (ie extract all words that are ALL CAPS and deduplicate them). Thoughts?

"JobConfigurationExtract": {      ...      "properties": {        "compression": {          "description": "Optional. The compression type to use for exported files.Possible values include DEFLATE, GZIP, NONE, SNAPPY, and ZSTD. Thedefault value is NONE. Not all compression formats are support for allfile formats. DEFLATE is only supported for Avro. ZSTD is only supportedfor Parquet. Not applicable when extracting models.",          "type": "string"        },

Agreed. Without a structured representation of the allowed values, it's too fragile.