Summary

When a new schema version is introduced in unified-test-format, new spec documents tend to be stamped with the latest version even if the document does not use the new fields of the new versions.

Example with command-logging-and-monitoring/tests/monitoring/writeConcernError, this file is valid with schemaVersion 1.4 but it have been created with schemaVersion 1.13

Motivation

Who is the affected end user?

Driver developers have to implement the test logic of the new versions even if their task is to implement an unified test case that doesn't require it. Alternatively the "max supported schema version" can be artificially updated.

https://github.com/mongodb/mongo-php-library/pull/1090#discussion_r1213254002

How does this affect the end user?

Require more work than necessary for driver developers.

How likely is it that this problem or use case will occur?

Every time a new unified test is added without checking the minimum schema version required.

If the problem does occur, what are the consequences and how severe are they?

Developer efficiency or test reliability issue.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes.

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?