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.
The current behaviour is that assertions are disabled by default when running tests. The only fix that I am aware of is to add the vmargs "-ea" to each project. However, this has the disadvantage that it is not a global setting and forces main classes to also run with assertions enabled. I believe that assertions should be enabled by default for the junit tasks. (e.g. by adding <jvmarg line="-ea"/> to the <junit> when JDK >= 1.4).
has this been assigned to anybody?
So everybody is ok with assertions being disabled by default for runs of Unit tests? The only workaround that I know of is to add '-ea' to the run parameters, which obviously mean that the live run has assertions... not good.
See details about fix in the Bug 175517