• Create a new -dryRun diff resmoke command which tells you any tests your changes will start/stop running & run this command as part of every resmoke run in CI. This will make it easy for engineers to see how their changes affect the tests that are run. If -dryRun diff is giving unexpected results, it is almost certainly an infrastructure issue that needs to be addressed by SDP.
• Appendix: Resmoke –-dryRun diff

• Have a dry_run_multiversion_light_up variant which runs *dryRun diff* on every multiversion task. If there is any diff in the tests to run, it will fail the task & print the diff. This variant can be used as a quick way for engineers to see if the jsTest they added affects any multiversion tasks or not. It will not be a required variant, just something purely used for seeing what new tests will run on a per task basis.

We've looked into burn-in-tags & have decided this sends a better signal on whether a devs jstest changes will introduce multiversion failures (or other failures) or not. Instead, we've decided to expand burn-in-tags coverage to all required and suggested variants.

A separate task-generator ticket will be done in conjunction with this to make the UX more clear that jstests have been affected as a result of the current changes.