Community
Participate
Working Groups
Unused import statements remain in generated test suite class when removing behaviors from the test suite. For example, create a loop in the Behavior tabbed pane of the JUnit test suite editor, the code generator adds the loop to the generated test suite class and the necessary import (import junit.extensions.RepeatedTest;), however, when the user removes the same loop, the import statements remains in the generated test suite class.
Deferring to i3.
Need the architectural change described in bugzilla 134254 to implement this (the JDT model does not allow to compute unused imports, this is only feasible with AST). Deferring to 4.3.
Reassigning to the component leads to triage for 4.4.
Targeting to future since not containable in 4.4.
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.
Correction: The Test Project mailing list is tptp-testing-tools-dev@eclipse.org.
In org.eclipse.hyades.test.tools.core.internal.java.codegen.JUnitGenerator.createSourceUpdateChange(IFile, SubProgressMonitor), we will need to invoke the equivilent of an org.eclipse.jdt.internal.corext.codemanipulation.OrganizeImportsOperation after the call to helper.emitSortedImports(cu).
We want to revisit this defect in 4.5 since it is impacting our own testing process. When Project Leads and committers remove invocations of test suite from their JUnit-based test suite, removing the plug-in under test causes compilation errors.
Deferring to future as approved by the TPTP PMC (http://dev.eclipse.org/mhonarc/lists/tptp-pmc/msg04926.html).
Reproducible in TPTP-4.6.0-200906191311
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
Reopening since still relevant.
Closing.
