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.

Bug 51367 - Add support for profiling JUnit tests in 4.0
Summary: Add support for profiling JUnit tests in 4.0
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC All
: P3 blocker (vote)
Assignee: iformanek
URL:
Keywords:
: 59087 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-11-10 09:42 UTC by iformanek
Modified: 2007-02-12 21:59 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description iformanek 2004-11-10 09:42:21 UTC
The profiler does not allow to profile JUnit 
tests in 4.0
Comment 1 iformanek 2004-11-10 09:42:56 UTC
Accepting the issue for M4
Comment 2 iformanek 2004-12-13 13:40:08 UTC
Will add in M5
Comment 3 iformanek 2005-01-19 09:20:09 UTC
Changing issue type to Task
Comment 4 iformanek 2005-01-19 09:20:26 UTC
Changing issue type to Task
Comment 5 iformanek 2005-01-19 09:21:08 UTC
Feature actually
Comment 6 iformanek 2005-02-03 01:08:07 UTC
Target milestone TBD
Comment 7 ehucka 2005-05-23 10:03:21 UTC
*** Issue 59087 has been marked as a duplicate of this issue. ***
Comment 8 _ gtzabari 2005-05-23 15:30:59 UTC
Someone should revise the target milestone. Is this feature a lot of work to add?
Comment 9 iformanek 2005-06-09 14:44:00 UTC
I started implementing this, if I won't run into any problems this will be done 
in M7.

The "Profile Test" action will likely behave similarly to "Run Test", just 
running the app in profiler with the selected instrumentation.
Comment 10 iformanek 2005-06-19 11:13:24 UTC
Postponing to M8
Comment 11 iformanek 2005-07-20 13:38:29 UTC
Done in M8, now it is possible to use Profile | Profile Other | Profile Test to 
profile JUnit tests.
Comment 12 fullung 2005-09-24 04:21:39 UTC
I think this feature is difficult to use.

How would I go about profiling a test runner?

How does NetBeans figure out when a class is a test for another class?
Comment 13 ehucka 2006-10-09 12:08:53 UTC
Verification of old issues.
Comment 14 Alexander Kouznetsov 2007-02-12 21:59:55 UTC
Closing old issues.