Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 41651

Summary:	[JUnit] need better indication of which tests to run
Product:	[Eclipse Project] JDT	Reporter:	Adam Kiezun <akiezun>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	dirk_baeumer, ekuleshov, mlq.eclipse
Version:	3.0	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Adam Kiezun

2003-08-18 11:48:17 EDT

20030813
i have more than 2500 tests and everytime i change something i'd like to know 
which tests to run. currently, there's no support for it, so the important task 
of running all relevant tests before releasing is often forgotten, because it 
takes so much effort to locate the affected tests.

i'd be very happy with an approximation that would show the affected suites, 
not precisely the test cases and false positives are fine with me.

Comment 1 Dirk Baeumer

2003-08-18 11:56:30 EDT

I second this!. Is there something we can do for 3.0.

Comment 2 Erich Gamma

2003-08-18 12:33:55 EDT

Count me in - minimal regression suites is an interesting research topic, see 
http://www.research.ibm.com/people/t/tip/abstracts/cia.html as an example.

Comment 3 Adam Kiezun

2003-08-18 12:41:29 EDT

like i said, 'minimal' is not an issue for me. any resonable (i.e. useful) 
superset of that minimal would be better than what we have now.

how'bout collecting the info dynamically on running the tests for the first 
time and use that (if test testXXX in suite S reaches class Y, then if Y 
changes, you have to run S)? That would give you both false positives and true 
negatives but still better than nothing at all. Such a feature would be a huge 
time-saver for me.

Comment 4 Erich Gamma

2003-08-18 17:39:21 EDT

*** Bug 41617 has been marked as a duplicate of this bug. ***

Comment 5 Eugene Kuleshov

2003-08-18 18:50:59 EDT

This functionality probably can be done with either static or dynamic 
dependency checking. Unfortunately there could be some issues with Java 
reflection and dynamically generated code (even so, such things not suppose to 
be part of unit testing).

Comment 6 Eugene Kuleshov

2006-05-23 18:40:42 EDT

Erich, should this issue also be reassigned to Markus?

Comment 7 Erich Gamma

2006-05-24 05:38:05 EDT

moving back to inbox

Comment 8 Martin Aeschlimann

2006-05-24 16:00:26 EDT

setting to later, help wanted

Comment 9 Denis Roy

2009-08-30 02:15:24 EDT

As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.