Summary

As Andreas noted in mongodb/mongo-php-library#854, the unified test format specifies a particular order for evaluating runOnRequirements. It may not be necessary to be strict about the order of evaluation, and at the very least we can re-order certain checks to be more efficient. For example, checking an environment variable (e.g. serverless) is quite cheap and could be done before communicating with any server to check something like a topology or version.

Motivation

Who is the affected end user?

Drivers implementations of unified test runner.

How does this affect the end user?

Inefficient test execution.

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

Every check of runOnRequirements.

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

Inefficiency.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes.