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.
Creating a new module project automatically creates the directory structure for unit tests, so all modules have subnodes in the project view for "Unit Test Packages" and "Unit Test Libraries." This is not true for functional tests; they are not created automatically nor is there any way to add support for them via the UI. I don't think this should be created by default, since not all modules are visual, but it would be a welcome enhancement to create them on demand. This could be as simple as having a New File template for a sample functional test. However, I am filing this as a defect because the only workaround of which I am aware does not work correctly. You can add support for functional tests to a module by switching to Files view and creating the test/qa-functional/src hierarchy. Doing this does not seem to add the the "Functional Test Packages" and "Functional Test Libraries" to the module until the IDE is closed. Therefore, it's not possible to add the necessary functional test dependencies (jemmy, jelly tools, etc.) unless you either restart the IDE or edit the project.xml manually to add them.
On a related note, adding dependencies for qa-functional tests also does not seem to update the classpath as described here: http://www.netbeans.org/issues/show_bug.cgi?id=165098 After adding the test/qa-functional/src directory structure as described and then restarting the IDE so I could see it, I added functional test dependencies on the Jemmy, Jellytools Platform and NBJunit modules. I got "red squigglies" in the editor indicating that Jellytools Platform was not actually in the classpath (although import statements for NBJunit and Jemmy classes seemed to be OK). This problem persisted until I restarted the IDE; after the restart and a few seconds of project scanning, the req squigglies and error badge on the TopComponent and in the project tab went away.
Yes, it is a known issue. *** This issue has been marked as a duplicate of 143633 ***