Before working on actual features, add the E2E tests outlined in the test plan and ensure they fail:

Create resmoke unit tests that will test these scenarios:

• Run a single test using a resmoke fixture (simulating a test timeout)
• Run multiple tests using a resmoke fixture (simulating a task timeout)
• Run a test using mongorunner to spin up mongods (simulating a non-fixture test)

For each test, the script that sends a signal to resmoke will be called. The same script waits for those processes to have exited. Once they have, we will inspect that the analysis and archival has been done for all cases above. This should test everything except for evergreen calling it’s timeout task.

When beginning to add project features, ensure they pass these tests.