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 34925 - Enable detection that IDE was fully initialized
Summary: Enable detection that IDE was fully initialized
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords: T9Y
Depends on:
Blocks:
 
Reported: 2003-07-14 14:49 UTC by Jiri Skrivanek
Modified: 2008-12-22 23:11 UTC (History)
7 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Main.main waits for the end of execution (2.08 KB, patch)
2003-07-16 14:54 UTC, Jaroslav Tulach 		Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2003-07-14 14:49:56 UTC 
For UI testing it is important to know that
initialization of IDE was finished. It will
satisfy a better stability of tests. Maybe it is
sometimes not easy to say when IDE is initialized
but any attempt to specify such a moment is helpful.
Comment 1 Jaroslav Tulach 2003-07-15 09:24:35 UTC 
It is probably necessary to specify what is meant by "finished".
Usually people mean that main window is opened and ready to use. Still
after that a set of tasks is being executed (warm up). Do these matter
or not?
Comment 2 Jiri Skrivanek 2003-07-15 09:55:03 UTC 
Yes, warm up tasks matter. Especially when they can refresh some part
of UI (e.g. module installation). Even if they do nothing with UI, it
would be nice to know that something happens on the background because
it can influence speed of tested UI operations. So, "finished" means
that no process is running in IDE (except periodical ones).
Comment 3 Jesse Glick 2003-07-15 15:42:36 UTC 
BTW -J-Dnetbeans.warmup.skip=true can be used to suppress warm-up
tasks if desired.
Comment 4 Jaroslav Tulach 2003-07-16 14:53:39 UTC 
As the correct definition of "fully initialized" is a litle bit fuzzy
and the request comes from test group, I suggest to implement this in
xtest. It will need a little bit of help from core, but that should be
very simple.

I am attaching a diff that prints out "FINISHED!!!" close to the exact
time that we want to identify (right now a second or two before main
window is opened). To improve the time of the notification, the window
system guys could put some waits into the main initialization thread
and wait until whole window system is finished. That should be pretty
easy.
Comment 5 Jaroslav Tulach 2003-07-16 14:54:21 UTC 
Created attachment 10994 [details]
Main.main waits for the end of execution
Comment 6 Martin Brehovsky 2003-08-20 16:26:15 UTC 
Preliminary tests with XTest and the patch seem to work ok. I think
the patch should be comitted to cvs.
Comment 7 Jaroslav Tulach 2003-08-22 13:09:22 UTC 
/cvs/core/src/org/netbeans/core/Main.java,v  <--  Main.java
new revision: 1.170; previous revision: 1.169
done
Checking in src/org/netbeans/core/TopThreadGroup.java;
/cvs/core/src/org/netbeans/core/TopThreadGroup.java,v  <-- 
TopThreadGroup.java
new revision: 1.20; previous revision: 1.19
done
Comment 8 Jiri Skrivanek 2003-09-26 13:47:22 UTC 
Verified.