Problem: We have seen that with some frequency, developers add tags like requires_fcv_82 to tests in jstests/multiVersion with the intent of "I want the MongoDB Server binaries to be at least v8.2". However, this will actually fully exclude the tests so they never run in any EVG "multiversion" suite, because the generated resmoke invocation for that suite in a Server EVG patch looks as follows:

buildscripts/resmoke.py run -suites=multiversion --continueOnFailure -excludeWithAnyTags=...,requires_fcv_81,requires_fcv_82,requires_fcv_83,requires_fcv_90

It seems the actual meaning of those tags is "I want a MongoDB Server binary whose FCV can not go below 8.2".

SERVER-128742, SERVER-128743, SERVER-128744 show how this confusion has removed test coverage for multiple features.

During development, this issue slips through silently, because:

• A local resmoke invocation of the multiversion suite does not exclude those tags, so the test appears to run fine.
• During PR review, the required EVG patch will not show any test failure, since the test is excluded by the tags.
• When enabling a feature flag there is a linter that forces changing featureFlagX tags to requires_fcv_xx tags but that replacement actually makes the test not run anymore.

Solution: We should make this issue evident during development, e.g.:

• Add a linter that fails if adding a multiversion test tagged in a way that always excludes it from the suites.
• Ensuring the applied exclude tags match between local resmoke runs and EVG would also substantially reduce the impact.