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.
Would like to see the following enhancements to Unit Testing in Netbeans to make testing of MIDlets easier. 1) Fix 80623 - a show stopper that prevents use of Netbeans' built-in unit test support 2) Make it possible to create TWO JAD/JARs for a particular Project Configuration - one with, and one without UnitTest support: - To get the most out of testing, we want to be able to test JAD attributes set in the Project Configuration to make sure that they have been set correctly. This means that we have to include the unit test MIDlet with the main MIDlet when creating the build. We obviously don't want customers to see the test MIDlet, so after testing is complete, we need to remove that MIDlet from the build. The problem is that we have to edit the build configuration, that exposes us to errors from fat-fingering certain Configuration settings by accident, o I'r including a change when the Configuration is rebuilt to produce the test-free MIDlet. - Doing this would require several things: -- One suite (JAR/JAD) has the test MIDlet in the suite, and one does not -- ProGuard should be employed to remove the test classes from release package. 3) Make it possible to put the source for the test in a different folder (as appearing in the Projects pane) than the Source folder. Arguably we'd also like to be able to store the test source in a completely different directory tree than the program source as well. So we'd like to see a "Test Sources Location" textbox added to the General category of the Project Properties window. 4) Since I'm making a list, it would also be nice to have a similar folder arrangement for Javadoc. This is because if you include Javadoc package and overview html files in the sources, or images that are used to augment text descriptions in the Javadoc, these files will automatically be packaged in the JAD/JAR. It is important in a limited environment that these files NOT be packaged in the JAD/JAR. Please bump this to NB 6.5 or 7.0 if those versions does not address this. I am using 6.1, the current official release.
Thanks for suggestions we are going to evaluate it as soon as it's possible.