Bug 152428 - [JUnit] Loading list of available UnitTests takes a long time
Summary: [JUnit] Loading list of available UnitTests takes a long time
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Markus Keller CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-01 04:35 EDT by Dominik Stadler CLA
Modified: 2022-06-15 16:23 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Stadler CLA 2006-08-01 04:35:38 EDT 
When I have a number of JUnit-Tests in my workspace, when I go to Run-Run... and select a test-case target that has "run a single test" selected and then press "Search" to search for an existing testcase, this search takes a long time, sometimes up to a few minutes. 

This is tedious if you are e.g. manually re-testing a list of testcases that failed in an automated run, as you are always forced to wait a few minutes until you can run the next testcase. Maybe this information can be cached in the class-cache so that the search is done on available data.
Comment 1 Eclipse Genie CLA 2020-06-04 16:20:26 EDT 
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.
Comment 2 Eclipse Genie CLA 2022-06-15 16:23:59 EDT 
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.