Community
Participate
Working Groups
Build Identifier: 20120216-1857 For a project with a medium/large number of test classes (most projects), finding a Test Class by clicking on `Search` in a JUnit Run Configuration will take up to 5 seconds. This is because (as far as I can tell), the project is scanned for the test classes (and an index/cache is created from scratch) each time the Search button is pressed. Instead, this list/index of test classes should be precalculated and cached and just displayed when the user presses on Search. This would be a significant improvement to an action that is clearly one of the most useful and frequent actions a user does (picking and running tests), and, for any large project, the time the action takes now is indeed very long (I have experienced a 10 second delay until the list is even displayed on a large project). Reproducible: Always
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
