[DRIVERS-1885] Allow flexible order when evaluating runOnRequirements Created: 16/Aug/21  Updated: 28/Oct/23  Resolved: 26/Aug/21

Status: Closed
Project: Drivers
Component/s: Unified Test Runner
Fix Version/s: None

Type: Improvement Priority: Unknown
Reporter: Jeremy Mikola Assignee: Jeremy Mikola
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Driver Changes: Not Needed

 Description   

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.



 Comments   
Comment by Githook User [ 26/Aug/21 ]

Author:

{'name': 'Jeremy Mikola', 'email': 'jmikola@gmail.com', 'username': 'jmikola'}

Message: DRIVERS-1885: Allow runOnRequirement conditions to be evaluated in any order (#1052)
Branch: master
https://github.com/mongodb/specifications/commit/ad76c1f15e1ef5f22cc1e912d6394405fc579018

Comment by Jeremy Mikola [ 23/Aug/21 ]

https://github.com/mongodb/specifications/pull/1052

Generated at Thu Feb 08 08:24:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.