While working on the CQF project, it is expected that changes to optimizer-related areas will cause multiple changes in many CQF-related tests. Developers should be able to quickly and conveniently run all tests specifically written to test CQF in order to quickly isolate and investigate these changes, update expected results, and rerun the same tests.

This iterative process should be done locally on each developer's machine before starting a more extensive test on Evergreen.

Ideally CQF tests should be run via one or two resmoke commands (one for unit tests, and one for JS tests).

The addition of new tests should either happen automatically by virtue of adding them to certain directories, or there should be clear documentation how to do that, and it should be a requirement for each CQF task to make sure new tests are added to the CQF-specific setup.