-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Programmability
-
Programmability 2024-11-25
Once we've identified all of the SP unit tests and jstests we want to include in the smoke test suite, we'll need to create some runnable artifact that can run all of the tests. This will likely take the form of a script that runs the unit tests via ninja (assuming a build is already set up) and then runs any jstests with the appropriate suites using resmoke.
Note that any jstests we include in the suite should run in the commit queue. Unit tests already run in the commit queue.