In the long term, we will need to maintain the curated list of tests in the RSS Sydney smoke suite. This puts additional burden on developers to be aware of the tests and consider all newly added tests as potential contributions to the suite.

This is error prone and kinda tedious. If we can write a script to automatically generate the test suite, we could periodically run it.

It's not super clear how easy this is, but let's give it a try.

Milestones:

•  [DONE] Identify the js tests owned by our team
• Associate each js test with it's suite
  • We don't need to parse the suites files, we can probably get away with a static map of folder prefix -> suite name, e.g. jstests/noPassthrough -> no_passthrough
• Generate a fake yml file with ALL of our tests
• Run the smoke tests
  • In the output of the smoke tests, it has each test with it's runtime
• Using the output, generate a new yml file which only includes the js tests that run under some time limit (configurable).

In theory this would take a while to run since it runs the slow tests, but would generate a smoke suite that runs quickly.

Extensions:

• Have a hardcoded list of tests we want to include/exclude regardless of the runtime