Community
Participate
Working Groups
The JUnit test type is very difficult to use in practical application, because anytime you add a new test case, you need to regenerate the test, and regenerating the test overwrites all of the test code you have written. Fix this to not overwrite exiting testcase method bodies.
update based on requirements group review
This will be resolved by this one: 74796 (JUnit on top of JDT) The best is to ignore it, no?
Now that we have a "3.3" Version in bugzilla, updating bugzillas targeted to 3.3 or a 3.3 iteration so that their Version matches their Target. "future", "unspecified", "4.0", and "4.1" Versions will not be updated.
Implemented in 3.3 and 4.0 repositories. In TPTP 4.0, this change will be further completed by changes implied by bugzilla 74796.
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.