From ticket 843444

1. For each test to be executed it must load the entire project. When scheduling a single test from a project with 1000’s of tests, this becomes difficult.
2. Execution of a test depends on other tests that are not part of the execution. If two independent tests are created, a compilation error in one will halt execution of another, even if the other tests is not used in any way.
3. The larger a project becomes the slower the UI is to react to changes. Currently we wait on each load for 499 tests to be opened and an alert on “extracting elements.” This has been taking longer and longer as we increase the size and scope of our project. Splitting projects is an option, albeit non-optimal as this makes it more difficult to manage the tests as a whole. We would like to create indepenant tests then assign it to a project, instead of having a project with a multitude of tests that can not be shared.
4. We have previously run into memory limitations when loading a large project, exceeding 2gb of ram regularly when creating a modifying tests within test studio. This has resulted in crashes and other unwanted behavior.