Community
Participate
Working Groups
In rare circumstances, JUnit tests may not appear under the "Regular JUnit Test" node whereas they should. Workaround: open the file, make a modification to it, and save it.
Raising priority to P1 as the problem now appears as a larger problem: there are a couple of issues with the TestProvider class, that also causes other defects such as https://bugs.eclipse.org/bugs/show_bug.cgi?id=160971
Please target to 4.4 since all non-blocking/critical defects will be deferred as decided in today's AG call.
Reassigning to the component leads to triage for 4.4.
Targeting to future since cannot be contained 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.
Jerome/Julien, if you feel this defect should be included in 4.4 (e.g. not covered by the fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=160971), please provide the necessary reasoning for discussion on next week's Test Project call. For now, I am reducing the priority to P3 since it is currently not a 4.4. candidate defect.
Using the 4.5.0-200801210400 build, this problem cannot be reproduced.
Closing by default since not closed by the originator in the 7+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.
