The team in charge of the Catalog & Routing asset is planning to introduce a slew of core JS tests to cover the behavior of key functionalities in sharded clusters.

Some of the test cases require the running suite to provision a minimum number of nodes (in terms of shards and/or mongos) for correctly working. This could be expressed today by manually curating a new set of exclusion tags (under the requires_x_or_more_shards and requires_x_or_more_mongos format) on each suites that matches the values of the num_mongos and num_shards fixture parameters,, but it is a cumbersome and error prone process that may easily break.

A better alternative would consist in having resmoke generate those tags at suite startup time by inspecting the configuration of the available fixture.