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 55451 - Provide a capability for offline testing of instrumentation
Summary: Provide a capability for offline testing of instrumentation
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on: 51274 51542 53730
Blocks:
  Show dependency tree
 
Reported: 2005-02-24 06:12 UTC by mishadmitriev
Modified: 2009-05-25 21:03 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mishadmitriev 2005-02-24 06:12:41 UTC
VM developers who do the VM-side work for us need
to be able to run some relatively complex tests
with JFluid, without a need to bring up the GUI
and press buttons in it.

We can probably provide an initial version of such
an offline testing tool by implementing a switch
in the existing standalone tool that will make it
immediately start a preconfigured test without
bringing up the GUI, and shut down once the test
program is finished.
Comment 1 iformanek 2005-02-24 06:17:22 UTC
Actually we need to do this for the automated tests as well, so I'd
create a new separate testbed application that would control the
profiler engine in a non-gui fashion (essentially a different impl of
the Profiler class). Self assigning for now.
Comment 2 iformanek 2005-04-06 15:20:20 UTC
This is partially done in M6, the CLI tool exists and can be used to lauch the 
profiled app with certain instrumentation. However, working with results 
(specifically, saving for offline inspection via GUI and/or export into some 
sensible formats) waits for issues 53730, 51274 and 51542.

Postponing till M7 for this reason.
Comment 3 iformanek 2005-07-17 11:40:47 UTC
The part to be done in 1.0 is done, remaining work is future.
Comment 4 Tomas Hurka 2009-04-08 12:56:12 UTC
Milestone cleanup: future->next