This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Cannot run tests on 6.0 NetBeans Platform Application | ||
---|---|---|---|
Product: | apisupport | Reporter: | tomwheeler <tomwheeler> |
Component: | Project | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | brettryan, hsalameh, junit-issues |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
tomwheeler
2007-05-16 19:52:37 UTC
I verified this on a colleague's computer with M9 as well. It fails to effectively find JUnit as previously described. Both machines are running Windows XP, though I can try on Mac, Solaris, Linux and others if it is needed. moving this to IDE because that may be a better component. I just installed a recent daily build (20070528) and verified this problem still exists. A workaround is to set test.unit.cp.extra in each module's project.properties file to the path of a junit jar, e.g.: test.unit.cp.extra=${harness.dir}/extras/junit-3.8.1.jar However, this should not be necessary as it used to work out of the box in previous versions of NetBeans. I think we shouldn't limit what third party libraries can be used for tests. Some people will love Netbeans junits, most will prefer junits (some 3.8 and others 4.0), others will want to use mock libraries (easymock, jmock...) and so on. My suggestion is to make third party libraries for tests configurable the same way as we configure them for normal applications. Eduard *** This issue has been marked as a duplicate of 108686 *** |