Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 41617 - Incremental execution of JUnit tests [JUnit]
Summary: Incremental execution of JUnit tests [JUnit]
Status: RESOLVED DUPLICATE of bug 41651
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Erich Gamma CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-15 11:39 EDT by Eugene Kuleshov CLA
Modified: 2003-08-18 18:46 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Kuleshov CLA 2003-08-15 11:39:15 EDT
It will be very convenient to have an option to run JUnit tests incrementally. 
Now if you change some files JUnit results marked as changed, but it is 
difficult to say which tests were affected. 

Eclipse already have dependency checker used in java compiller, probably JUnit 
can reuse this information and rerun only affected tests. This feature, if it 
could be implemented may give java developer live view to the code status (of 
course if unit tests are fast enough and have good granularity).

Another convenient feature will be an option to run selected test from JUnit 
view without cleaning up all test results. This will be very helpful for 
resolving multiple issues at the same time.
Comment 1 Eugene Kuleshov CLA 2003-08-18 06:34:35 EDT
I'm not sure if first part of my description is related to UI. It seems quite 
fundamental issue and may require additional research.
Comment 2 Erich Gamma CLA 2003-08-18 17:39:21 EDT

*** This bug has been marked as a duplicate of 41651 ***
Comment 3 Eugene Kuleshov CLA 2003-08-18 18:46:56 EDT
Hmm, it seems that this request were filled few days before 41651... Who was 
the duplicate then? :-)

Anyway, I will be glad to see this functionality implemented. Thank you.