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

Bug 164486

Summary: Same file is displayed twice under the test navigator
Product: z_Archived Reporter: amehrega
Component: TPTPAssignee: Bozier jerome <jerome.bozier>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: paulslau
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: closed471
Bug Depends on: 156858    
Bug Blocks:    
Attachments:
Description Flags
Duplicated entry under the test navigator none

Description amehrega CLA 2006-11-14 11:15:23 EST 
Build: TPTP-4.3.0-200611070100

1) Create a Java project with a src folder
2) Create a regular JUnit under the src folder (make sure that you have the right Jar files under the java project classpath)
3) Switch to the test perspecitve
4) Click the logical toolbar of the test navigator
5) Expand the project > Regular JUnit Test > src
6) Right click a package under the src director and select New > Other > Java > JUnit > JUnit Test Case > Next > Specify a name and click on finish

Notice that the file is displayed twice in the test navigator (see the image attached)
Comment 1 amehrega CLA 2006-11-14 11:18:51 EST 
Created attachment 53825 [details]
Duplicated entry under the test navigator
Comment 2 Paul Slauenwhite CLA 2006-11-14 16:15:18 EST 
Ali, is this in fact a major severity?
Comment 3 amehrega CLA 2006-11-14 16:53:48 EST 
It's confusing to see two resources of the same name displayed under the navigator.  Deleting one will remove both.
I think it can be marked down to a normal because it doesn't prevent any function from being used but it should definitely be considered for 4.4.
Comment 4 Paul Slauenwhite CLA 2007-01-16 10:26:13 EST 
Reassigning to the component leads to triage for 4.4.
Comment 5 Paul Slauenwhite CLA 2007-01-26 08:25:27 EST 
Targeting to future since not containable in 4.4.
Comment 6 Paul Slauenwhite CLA 2007-01-26 09:01:36 EST 
As discussed on this week's Test Project call (January 22, 2007), the Test Project will focus on existing P1 - P2/Blocker - Major and P1/Normal and test creation/automation defects (omitting defects dependant on outstanding features) in TPTP 4.4.  All other Test Project defects have been targeted to future.

If this defect has been targeted to future and you/originator feel it should be completed in 4.4, please provide the necessary reason as a reply to this comment or a post to the Test Project mailing list (tptp-test-tooling-dev@eclipse.org).  We will collectively triage and assess our resources to determine a case-by-case decision.
Comment 7 Paul Slauenwhite CLA 2007-01-26 09:04:08 EST 
Correction:  The Test Project mailing list is tptp-testing-tools-dev@eclipse.org.
Comment 8 Paul Slauenwhite CLA 2008-06-27 13:57:17 EDT 
This defect is still reproducible in TPTP 4.5.0 (http://www.eclipse.org/tptp/home/downloads/?ver=4.5.0).
Comment 9 Paul Slauenwhite CLA 2009-06-09 08:30:41 EDT 

*** This bug has been marked as a duplicate of bug 274496 ***
Comment 10 Kathy Chan CLA 2010-11-18 23:27:29 EST 
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.