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.
I cannot profile performance/j2se/test/qa-functional/src/org/netbeans/performance/j2se/MeasureJ2SEActionsTest.java The system is probably confused by the class not extending TestCase. Wrong, suite method is enough. If I change the class to extend NbTestCase, then the profiling starts, but fails quite quickly for reasons unknown to me.
Could you, please, provide steps to reproduce? When I try to run/debug the performance/j2se/test/qa-functional/src/org/netbeans/performance/j2se/MeasureJ2SEActionsTest.java file I always end up with compilation error stating that "package org.netbeans.modules.project.ui.test does not exist" :( The hole IDE is up to date and compiled
I had this problem as well. I guess it is enough to go to the provider of 'org.netbeans.modules.project.ui.test' package and compile/run its tests. However I agree that this is needlessly complicated, I am CCing Oleg to see why we need to make it easier.
yes, we use ProjectSupport from org.netbeans.modules.project.ui.test to open projects. And it needs to be compiled before test execution (on hudson4qe we use script for that). Actually there is a method in Jelly for project opening and we'll switch to it so that we don't need ProjectUI tests anymore. I've committed changes to j2se perf tests - you can compile it now without org.netbeans.modules.project.ui.test, and next week I will commit changes to other perf modules as well.
Product Version: NetBeans IDE Dev (Build 091105) Java: 1.6.0_17; Java HotSpot(TM) Client VM 14.3-b01 System: Windows Vista version 6.0 running on x86; Cp1252; en_US (nb) I'm unable to process this issue, running the MeasureJ2SEActionsTest.java doesn't seem to work at all for me. I've built the full IDE, opened J2SE Performance Tests project, right-clicked org.netbeans.performance.j2se.MeasureJ2SEActionsTest node and selected Run File / Debug File / Test File. Neither of the actions work: E:\Sources\NetBeans\profiler-main\nbbuild\netbeans\harness\common.xml:528: The following error occurred while executing this line: E:\Sources\NetBeans\profiler-main\nbbuild\netbeans\harness\common.xml:472: Missing test dependency Runtime classpath: E:/Sources/NetBeans/profiler-main/nbbuild/netbeans/platform11/modules/org-netbeans-api-progress.jar;[... very very very long classpath ...];E:/Sources/NetBeans/profiler-main/nbbuild/netbeans/ide12/modules/org-netbeans-modules-projectui.jar -missing-Module-Entries-: org.netbeans.modules.performance Compile classpath: E:/Sources/NetBeans/profiler-main/nbbuild/netbeans/platform11/modules/org-netbeans-api-progress.jar;[... very very very long classpath ...];E:/Sources/NetBeans/profiler-main/nbbuild/netbeans/ide12/modules/org-netbeans-modules-projectui.jar -missing-Module-Entries-: org.netbeans.modules.performance BUILD FAILED (total time: 1 second) Any suggestions how to proceed?
The profiler doesn't recognize MeasureJ2SEActionsTest.java as a test, a workaround is to update the class to extend NbTestCase. I assume this should be enough to start profiling, the "uknown reasons" failing the execution were likely caused by unrecognized qa-functional tests. This is now fixed in Issue 17473.
Correction: I meant Issue 174733, not Issue 17473.