Scenario: Monolithic Codebase

[Silic0nS0ldier]

Most JS ecosystem tooling works really well for small to moderately sized projects. However as the volume of code increases (closing in on 500MB and beyond) performance has considerably degraded.

Projects of this size typically have special tooling designed to handle the workload. Considerations should be made so that these massive projects can customise how tests are loaded (etc), without having to hack around the test framework.

The approach thus far should mean relatively few scaling issues, with 1 exception. The test context. The way test context for each test is persisted means that memory cannot be completely released. It should be possible to refactor this library to support releasing context data, once I've figured out how it works.