Non-existent schema version referred to as project default doesn't fail

Example: project bi-edw-pos-ticket, file etlunit.json.
Under features: {file: {reference-file-types: {}}}.
If a table in this object is provided a default-version, and it actually does not exist in the schema, a test that uses that table will not fail. It will simply default to the current default version as configured in the schema.