It has been recently observed that the override mechanism to include periodic replSetStepdown requests to the execution of ShardingTest-based suites is not working as expected, due to a typo (ReplSetTest instead of ShardingTest) in the logic that allows to inject an override to the fixture constructor. As a consequence of this, the sharding_csrs_continuous_config_stepdown is behaving "de facto" as its vanilla counterpart.