Performance Test Specification

Author: Marian Mirilovic
Version: 5.0
Last update: 11/15/2005
Introduction: This is intended as performance testing provided by QA. These tests will measure time that IDE spends by providing feedback or display appropriate informations. We will use this test cases to looking for memory leaks. At least test will be used as regression tests to report performance improvement done during release cycle.
Comment:

Table of Contents

• 1. Measure Startup time
• 2. Memory Consumption after startup
• 3. Other performance tests
• 4. Measure Actions
• 5. Measure Dialogs
• 6. Measure Menus

Measure Startup time Purpose: Run the IDE and measure startup time. Startup time is defined as the time between the moment of invoking the application start (when you press Enter at the end of your command line) and the moment when the main window is fully painted and responsive to user. Setup: Start IDE with clear userdir. # Test case Description 1 Measure startup time after first start of IDE [ automated ] The starting point is when the user hits the Enter on the end of the command line. This is done by taking time before run external process to run the IDE startTime=System.currentTimeMillis(); Runtime.getRuntime().exec(...) The command line we are running is bin\netbeans(.exe) --cp:a {path to performance-test-utilities.jar} --userdir {userdir} --jdkhome {jdkhome} -J-Dnetbeans.full.hack=true -J-Dorg.netbeans.log.startup.logfile={path to log file} -J-Dorg.netbeans.log.startup=tests -J-Dnetbeans.close=true -J-Dorg.netbeans.performance.waitafterstartup=5000 The IDE starts and we are measuring values of few subtasks (following data we are parsing from the log file after finishing measured instance of the IDE): IDE run - time started by the command line exec untill IDE main class starts ModuleSystem.readList finished - time spend by reading Module System's list Preparation finished - time spend by preparation Window system loaded - time spend by loading of Window System Window system shown - time spend by showing Window System The IDE is waiting to show the whole appropriatelly painted Main Window. This check is done in our instance of the Repaint Manager. RESULT: Startup time can't prolong during release cycle. 2 Measure startup time - second start [ automated ] Restart the IDE with already created user directory The starting point is when the user hits the Enter on the end of the command line. This is done by taking time before run external process to run the IDE startTime=System.currentTimeMillis(); Runtime.getRuntime().exec(...) The command line we are running is bin\netbeans(.exe) --cp:a {path to performance-test-utilities.jar} --userdir {userdir} --jdkhome {jdkhome} -J-Dnetbeans.full.hack=true -J-Dorg.netbeans.log.startup.logfile={path to log file} -J-Dorg.netbeans.log.startup=tests -J-Dnetbeans.close=true -J-Dorg.netbeans.performance.waitafterstartup=5000 The IDE starts and we are measuring values of few subtasks (following data we are parsing from the log file after finishing measured instance of the IDE): IDE run - time started by the command line exec untill IDE main class starts ModuleSystem.readList finished - time spend by reading Module System's list Preparation finished - time spend by preparation Window system loaded - time spend by loading of Window System Window system shown - time spend by showing Window System The IDE is waiting to show the whole appropriatelly painted Main Window. This check is done in our instance of the Repaint Manager. RESULT: Startup time can't prolong during release cycle. 3 Measure startup time - opened 10 java (20kB) files [ automated ] Close Welcome window. Open project jEdit Open 10 java (20kB) files and exit IDE. Restart the IDE The starting point is when the user hits the Enter on the end of the command line. This is done by taking time before run external process to run the IDE startTime=System.currentTimeMillis(); Runtime.getRuntime().exec(...) The command line we are running is bin\netbeans(.exe) --cp:a {path to performance-test-utilities.jar} --userdir {userdir} --jdkhome {jdkhome} -J-Dnetbeans.full.hack=true -J-Dorg.netbeans.log.startup.logfile={path to log file} -J-Dorg.netbeans.log.startup=tests -J-Dnetbeans.close=true -J-Dorg.netbeans.performance.waitafterstartup=5000 The IDE starts and we are measuring values of few subtasks (following data we are parsing from the log file after finishing measured instance of the IDE): IDE run - time started by the command line exec untill IDE main class starts ModuleSystem.readList finished - time spend by reading Module System's list Preparation finished - time spend by preparation Window system loaded - time spend by loading of Window System Window system shown - time spend by showing Window System The IDE is waiting to show the whole appropriatelly painted Main Window. This check is done in our instance of the Repaint Manager. RESULT: Startup time can't prolong during release cycle. 4 Startup Time with opened NB project results [ automated ] Close Welcome window. Open NB project SystemProperties Open 10 java (20kB) files and exit IDE. Restart the IDE The starting point is when the user hits the Enter on the end of the command line. This is done by taking time before run external process to run the IDE startTime=System.currentTimeMillis(); Runtime.getRuntime().exec(...) The command line we are running is bin\netbeans(.exe) --cp:a {path to performance-test-utilities.jar} --userdir {userdir} --jdkhome {jdkhome} -J-Dnetbeans.full.hack=true -J-Dorg.netbeans.log.startup.logfile={path to log file} -J-Dorg.netbeans.log.startup=tests -J-Dnetbeans.close=true -J-Dorg.netbeans.performance.waitafterstartup=5000 The IDE starts and we are measuring values of few subtasks (following data we are parsing from the log file after finishing measured instance of the IDE): IDE run - time started by the command line exec untill IDE main class starts ModuleSystem.readList finished - time spend by reading Module System's list Preparation finished - time spend by preparation Window system loaded - time spend by loading of Window System Window system shown - time spend by showing Window System The IDE is waiting to show the whole appropriatelly painted Main Window. This check is done in our instance of the Repaint Manager. RESULT: Startup time can't prolong during release cycle.

Memory Consumption after startup Purpose: Run the IDE run and measure memory footprint. Setup: Start IDE with clear userdir. # Test case Description 1 Memory Consumption After Start [ automated ] Start the IDE We are waiting for finish of the startup sequence and when the IDE is running we start to measure memory footprint, by checking size of memory occupied by netbeans process: Window use pslist.exe and take "MEM" Unix use ps and take "RES", "RSS" RESULT: Memory footprint size can't growth during release cycle. 2 Memory Consumption After Start with 10 opened files [ automated ] Close Welcome window Open project jEdit Open 10 java (20kB) files and exit IDE Restart the IDE We are waiting for finishing of the startup sequence and when the IDE is running we start to measure memory footprint, by checking size of memory occupied by netbeans process. We are using pslist.exe (windows) and ps (unix). Output of these commands is parsed and value (windows - "MEM", unix - "RES", "RSS") presents as measured memory memory consumption. RESULT: Memory footprint size can't growth during release cycle.

Other performance tests Purpose: Setup: Start IDE with clear userdir. # Test case Description 1 Measure classpath scanning time [ automated ] Close Welcome window. Close Memory Toolbar. Open project JEdit project Measure scanning of classpath roots. RESULT: Scanning of classpath roots can't prolong during release cycle. 2 Measure time of warmup tasks [ automated ] The command line we are running is bin\netbeans(.exe) --cp:a {path to performance-test-utilities.jar} --userdir {userdir} --jdkhome {jdkhome} -J-Dnetbeans.full.hack=true -J-Dorg.netbeans.log.startup.logfile={path to log file} -J-Dorg.netbeans.log.startup=tests -J-Dnetbeans.close=true -J-Dnetbeans.warm.close=true -J-Dorg.netbeans.performance.waitafterstartup=5000 The IDE starts and we are measuring deltas for each WarmUp task separately as well as the time of the whole WarmUp. The IDE is waiting to show the whole appropriatelly painted Main Window. This check is done in our instance of the Repaint Manager when WarmUp task has finished. RESULT: Check all WarmUp tasks and hold it under control

Measure Actions Purpose: Measure time until user did action that must finish by Open window, expand/collapse node, (un)mount filesystems, .... . We will measure time from last user event to last paint. Quotes for these actions are : 1000ms for Open window and 100ms for another actions (expand folder, ..). Setup: Start IDE with clear userdir. Close Welcome Window. Open one J2SE Project and one Web Project. # Test case Description 1 Expand Project node [ automated ] Switch to Projects view Expand project node JEdit project RESULT: Node is expanded within 1000 ms. 2 Expand Source Packages node [ automated ] Switch to Projects view Expand Source Packages of project JEdit project (22 packages) RESULT: Node is expanded within 1000 ms. 3 Expand folder with 50 java files [ automated ] Switch to Projects view Expand package with 50 java files RESULT: Package is expanded within 1000 ms. 4 Expand folder with 100 java files [ automated ] Switch to Projects view Expand package with 100 java files RESULT: Package is expanded within 1000 ms. 5 Expand folder with 100 txt files [ automated ] Switch to Projects view Expand folder with 100 txt files RESULT: Package is expanded within 1000 ms. 6 Expand folder with 100 xml files [ automated ] Switch to Projects view Expand package with 100 xml files RESULT: Package is expanded within 1000 ms. 7 Open Java file (20kB) [ automated ] Open java file (20kB) if source editor isn't opened RESULT: Editor is opened within 1000 ms. 8 Open Java file (20kB) if Editor opened [ automated ] Open java file (20kB) if source editor is opened RESULT: New tab in the Editor is opened within 1000 ms. 9 Open Txt file (20kB) [ automated ] Open txt file (20kB) if source editor isn't opened RESULT: Editor is opened within 1000 ms. 10 Open Txt file (20kB) if Editor opened [ automated ] Open txt file (20kB) if source editor is opened RESULT: New tab in the Editor is opened within 1000 ms. 11 Open Xml file (20kB) [ automated ] Open xml file (20kB) if source editor isn't opened RESULT: Editor is opened within 1000 ms. 12 Open Xml file (20kB) if Editor opened [ automated ] Open xml file (20kB) if source editor is opened RESULT: New tab in the Editor is opened within 1000 ms. 13 Open JSP file [ automated ] Open JSP file if source editor isn't opened RESULT: Editor is opened within 1000 ms. 14 Open JSP file if Editor opened [ automated ] Open JSP file if source editor is opened RESULT: New tab in the Editor is opened within 1000 ms. 15 Open Properties file (20kB) [ automated ] Open properties file (20kB) if source editor isn't opened RESULT: Editor is opened within 1000 ms. 16 Open Properties file (20kB) if Editor opened [ automated ] Open properties file (20kB) if source editor is opened RESULT: New tab in the Editor is opened within 1000 ms. 17 Open Form file (20kB) [ automated ] Open form file (20kB) if source editor isn't opened RESULT: Editor and Form Editor Window are opened as soon as possible. 18 Open Form file (20kB) if Editor opened [ automated ] Open form file (20kB) if source editor is opened RESULT: New tab in the Editor is opened within 1000 ms. 19 Paste text in the Editor Open java1 file [20kB] Open java2 file [20kB] Select text from java1 file and from popup menu push Copy Move cursor to java2 file and from popup menu push Paste|Copy RESULT: Text is pasted to java2 file within 100ms. 20 Page up in the Editor [ automated ] Open javax.swing.JTable file Move cursor to the last line Press Page Up key RESULT: Source Editor paint paged up view within 100ms. 21 Page down in the Editor [ automated ] Open javax.swing.JTable file Move cursor to the first line Press Page Down key RESULT: Source Editor paint paged up view within 100ms. 22 Let invoke code completion in java file [ automated ] Open java file Move cursor on text "System." and wait code completion RESULT: Code completion window should be opened as soon as possible. 23 Type character in the Editor [ automated ] Open java file Type character to opened source editor RESULT: Typed character should be written to editor area without delay. 24 Scrolling in the Editor (java [50kB]) Open java file [50kB] Scroll to the end of file in the Source Editor RESULT: File should be scrolled at final position as soon as possible. 25 Close Java file (20kB) [ automated ] Open java file in the editor (Source View is opened and it's the only one opened editor) Push Close Window from popup menu on tab RESULT: Source Editor is closed within 100 ms. 26 Close Form file (20kB) [ automated ] Open form file in the editor (Source View and Form Designer are opeend and they're the only two opened editors) Push Close Window from popup menu on Source View tab RESULT: Source Editor is closed within 100 ms. 27 Close All Window_Documents if 10 Java files opened [ automated ] Open 10 java files Push Close All Window_Documents from main menu RESULT: Source Editor is closed within 1000 ms. 28 Close on tab from Editor window [ automated ] Open more java files Push Close Window from popup menu on one before last Source View tab RESULT: Source Editor tab is closed within 100 ms. 29 Close modified Java file [ automated ] Open java file Modify code (write something to the opened document) Push Close Window from popup menu on the tab RESULT: Question dialog for asking to save before close is opened within 1000ms. 30 Save modified Java file [ automated ] Open java file Write something Push from popup menu Save RESULT: Status "Saving..." arise within 100ms. Edited file is saved within 1000ms, * disappears 31 Select GUI Forms category in New File [ automated ] Select folder node in Projects view Push from main menu File | New File... Select node Java GUI Forms in Categories view RESULT: File Types view shows list of templates for Java GUI Forms category within 1000 ms. 32 Select XML category in New File [ automated ] Select folder node in Projects view Push from main menu File | New File... Select node XMLs in Categories view RESULT: File Types view shows list of templates for XML category within 1000 ms. 33 Select Other category in New File [ automated ] Select folder node in Projects view Push from main menu File | New File... Select node Other in Categories view RESULT: File Types view shows list of templates for Other category within 1000 ms. 34 Open Java Application project Push File|Open Project... from main menu Write "TestApplication" project path to the File Name text field Push Open Project Folder button RESULT: "TestApplication" project node is displayed in Projects view within 1000 ms. 35 Open Java Library project Push File|Open Project... from main menu Write "TestLibrary" project path to the File Name text field Push Open Project Folder button RESULT: "TestLibrary" project node is displayed in Projects view within 1000 ms. 36 Open Web Application project Push File|Open Project... from main menu Write "TestWebApplication" project path to the File Name text field Push Open Project Folder button RESULT: "TestWebApplication" project node is displayed in Projects view within 1000 ms. 37 Open Java Project with Existing sources Push File|Open Project... from main menu Write "TestProjectWithExistingSources" project path to the File Name text field Push Open Project Folder button RESULT: "TestProjectWithExistingSources" project node is displayed in Projects view within 1000 ms. 38 Create Java Application project [ automated ] Push File|New Project... from main menu Select Standard node in Categories tree Select Java Application node in Projects tree Push Next button Write "TestApplication" to the Project Name text field Push Finish button RESULT: "TestApplication" project node is created in Projects view and Main java is opened in editor within 10000 ms. 39 Create Java Class Library project [ automated ] Push File|New Project... from main menu Select Standard node in Categories tree Select Java Class Library node in Projects tree Push Next button Write "TestLibrary" to the Project Name text field Push Finish button RESULT: "TestLibrary" project node is created in Projects view within 10000 ms. 40 Create Web Application project [ automated ] Push File|New Project... from main menu Select Web node in Categories tree Select Web Application node in Projects tree Push Next button Write "TestWebApplication" to the Project Name text field Push Finish button RESULT: "TestWebApplication" project node is created in Projects view within 10000 ms. 41 Create Java Project with Existing sources [ automated ] Push File|New Project... from main menu Select Standard node in Categories tree Select Java Project with Existing Sources node in Projects tree Push Next button Write "TestProjectWithExistingSources" to the Project Name text field Push Finish button RESULT: "TestProjectWithExistingSources" project node is created in Projects view within 1000 ms. 42 Create Module Project [ automated ] Push File|New Project... from main menu Select NetBeans Plug-in Modules node in Categories tree Select Module Project node in Projects tree Push Next button Write "Module Project" to the Project Name text field Push Finish button RESULT: "Module Project" project node is created in Projects view within 1000 ms. 43 Create Module Suite Project [ automated ] Push File|New Project... from main menu Select NetBeans Plug-in Modules node in Categories tree Select Module Suite Project node in Projects tree Push Next button Write "Module Suite Project" to the Project Name text field Push Finish button RESULT: "Module Suite Project" project node is created in Projects view within 1000 ms. 44 Create Module Suite Project [ automated ] Push Tools|Add to Favorites on node Main20kB.java in projects view RESULT: Main20kB.java node is added to Favorites and the same view is opene within 1000 ms. 45 Close Java Application project Open project "TestApplication" Push Close Project from popup menu on project node RESULT: "TestApplication" project node is removed form Projects view within 1000 ms. 46 Build Hello World project Write Hello World application : System.out.println("Hello World"); Set Hello World application as Main Project Push from main menu Build|Build Main Project RESULT: Status "Running ..." arise within 100ms. Application must finished as soon as possible. 47 Clean and Build Hello World project Write Hello World application : System.out.println("Hello World"); Set Hello World application as Main Project Push from main menu Build|Clean and Build Main Project RESULT: Status "Running ..." arise within 100ms. Application must finished as soon as possible. 48 Run Hello World project Write Hello World application : System.out.println("Hello World"); Set Hello World application as Main Project Push from main menu Run|Run Main Project RESULT: Status "Running ..." arise within 100ms. Application must finished as soon as possible. 49 Expand Container node in Component Inspector Open JFrame file Expand "JFrame" node in the Component Inspector RESULT: Node is expanded within 1000 ms. 50 Delete folder with 50 java files Push Delete from popup menu on package with 50 java files Push Ok on Confirm Object Deletion dialog RESULT: Package disappears from Projects view within 1000 ms. 51 Delete folder with 100 java files Push Delete from popup menu on package with 100 java files Push Ok on Confirm Object Deletion dialog RESULT: Package disappears from Projects view within 1000 ms. 52 Create New Java file Source Editor is closed Select test package in Projects view Push from main menu File | New File... Select category Java Classes and file type Java Main Class Press button Next Press button Finish RESULT: New Main java file is created and opened in the Source Editor within 1000ms. 53 Create New Java file if Editor opened Source Editor is opened Select test package in Projects view Push from main menu File | New File... Select category Java Classes and file type Java Main Class Press button Next Press button Finish RESULT: New Main java file is created and opened in the Source Editor within 1000ms. 54 Create New Package Select test package in Projects view Push from main menu File | New File... Select category Java Classes and file type Java Package Press button Next Press button Finish RESULT: New Main java file is created and opened in the Source Editor within 1000ms. 55 Minimize Projects window Push minimize button of Projects window in title bar RESULT: Projects view is minimized within 100ms. 56 Slide Projects window Minimize Projects window Push Projects view button from edge bar RESULT: Projects view is slided within 100ms. 57 Auto Hide Projects window Minimize Projects window Push Projects view button from edge bar Click inside opened editor window RESULT: Projects view is minimized within 100ms. 58 Show Members view of selected Java file (20kB) Select a java file in Projects view Select java file (20kB) in Projects view RESULT: Navigator window is repainted and Members View of selected class is shown in 100ms. 59 Show Inheritance view of selected Java file (20kB) Open java file (20kB) Change view from Members view to Inheritance view RESULT: Navigator window is repainted and Inheritance View of opened class is shown in 100ms. 60 Inheritance view of Java file (20kB) is shown Open java file (20kB) Change view from Members view to Inheritance view Select filter Show Inherited Members RESULT: Navigator window is repainted and Inheritance View with Inherited members of opened class is shown in 100ms. 61 Javadoc over method in Nevigator view is shown Open java file Let mouse over method main in Nevigator view RESULT: Javadoc of actually "selected" method is shown in 100ms. 62 Expand class node in Nevigator view Open java file Change view from Members view to Inheritance view Expand Object node RESULT: Tree of methods of Object class is shown in 100ms. 63 Step Over in debugger Open ColorPicker from examples folder Move cursor to 36th line and Run to Cursor Push Step Over RESULT: Step Over must finished within 100ms. 64 Find Usages Open JEdit project Push Find Usages... from popup menu on the node org.gjt.sp.jedit|JEdit Push Finish button in Find Usages dialog. RESULT: Usages window with all listed usages is opened as soon as possible. 65 Refactor_Rename Open JEdit project Push Refactor|Refactor_Rename from popup menu on the node org.gjt.sp.jedit|JEdit Push Finish button in Refactor_Rename dialog. RESULT: Refactor_Rename with all possible errors finished as soon as possible.

Measure Dialogs Purpose: Measure time until user did action that must finish by Open dialog/window. We will measure time from last user event to last paint. Limit for Open dialogs/windows is 1000ms. Setup: Start IDE with clear userdir. Close Welcome Window. Open one J2SE Project and one Web Project. # Test case Description 1 About dialog open Push Help | About RESULT: About Dialog is opened within 1000ms. 2 About details open Push Help | About Switch to the Detail tab RESULT: About Dialog switches within 1000ms. 3 Java Platform Manager open [ automated ] Push main menu Tools|Module Manager RESULT: Module Manager dialog is opened within 1000ms 4 Server Manager open [ automated ] Push main menu Tools|Server Manager RESULT: Server Manager dialog is opened within 1000ms 5 Template Manager open [ automated ] Push main menu Tools|Template Manager RESULT: Template Manager dialog is opened within 1000ms 6 Options dialog open [ automated ] Push main menu Tools|Options RESULT: Options dialog is opened within 1000ms. 7 New Project dialog open [ automated ] Push main menu File|New Project... RESULT: New Project dialog is opened within 1000ms. 8 New File dialog open [ automated ] Push main menu File|New File... RESULT: New File dialog is opened within 1000ms. 9 Open Project dialog open [ automated ] Push main menu File|Open Project... RESULT: Open Project dialog is opened within 1000ms. 10 Open File dialog open [ automated ] Push main menu File|Open File... RESULT: Open File dialog is opened within 1000ms. 11 Update Center wizard open [ automated ] Push main menu Tools|Update Center RESULT: The Update Center is opened within 1000ms 12 Proxy Configuration open [ automated ] Push main menu Tools|Update Center Push button Proxy Configuration RESULT: Proxy Configuration dialog is opened within 1000ms 13 Favorites window open [ automated ] Push main menu Window|Favorites RESULT: The Favorites window is opened within 1000ms 14 Files window open Push main menu Window|Files RESULT: The Files window is opened within 1000ms 15 Projects window open Push main menu Window|Projects RESULT: The Projects window is opened within 1000ms 16 Runtime window open Push main menu Window|Runtime RESULT: The Runtime window is opened within 1000ms 17 Versioning window open [ automated ] Push main menu Window|Versioning RESULT: The Versioning window is opened within 1000ms 18 Output window open Push main menu Window|Output RESULT: The Output window is opened within 1000ms 19 To Do window open [ automated ] Push main menu Window|To Do RESULT: The To Do window is opened within 1000ms 20 Http Monitor window open [ automated ] Push main menu Window|HTTP Monitor RESULT: The HTTP Monitor window is opened within 1000ms 21 Help Contents window open [ automated ] Push menu Help | Help Contents RESULT: Help Window is opened within 1000ms, "Welcome to the Online Help" page is shown. Title is "Help All". Contents tab is selected. 22 String Property Editor open [ automated ] Open testing properties sheet TestProperties Invoke property editor for String property RESULT: String property editor is opened within 1000ms. 23 Color Property Editor open Open testing properties sheet TestProperties Invoke property editor for Color property RESULT: Color property editor is opened within 1000ms. 24 Add JDBC Driver dialog open [ automated ] Open Runtime view and select Databases | Drivers node Push from popup menu Add Driver ... RESULT: Add JDBC Driver dialog is opened within 1000ms. 25 New Database Connection dialog open [ automated ] Open Runtime view and select Databases | Drivers | JDBC-ODBC Bridge node Push from popup menu Connect Using ... RESULT: New Database Connection dialog is opened within 1000ms. 26 Add Catalog dialog open [ automated ] Open Runtime view and select DTD and XML Schema Catalogs node Push from popup menu Add Catalog... RESULT: Add Catalog dialog is opened within 1000ms. 27 Find in Projects dialog open [ automated ] Select project node in Projects view Push main menu Edit|Find in Projects... RESULT: Find in Projects dialog is opened within 1000ms. 28 JSE Project Properties window open [ automated ] Select JSE Project node in Projects view Push from popup menu Properties RESULT: Project Properties window is opened within 1000ms 29 NB Project Properties window open [ automated ] Select NB Project node in Projects view Push from popup menu Properties RESULT: Project Properties window is opened within 1000ms 30 Web Project Properties window open [ automated ] Select Web Project node in Projects view Push from popup menu Properties RESULT: Project Properties window is opened within 1000ms 31 Delete object dialog open [ automated ] Open JEdit project Push Delete from popup menu on the node org.gjt.sp.jedit|JEdit RESULT: Confirm Object Deletion dialog is opened within 1000ms. 32 Attach dialog open [ automated ] Push main menu Run|Attach Debugger... RESULT: The Attach dialog is opened within 1000ms 33 New Breakpoint dialog open [ automated ] Push main menu Run|New Breakpoint... RESULT: The New Breakpoint dialog is opened within 1000ms 34 New Watch dialog open [ automated ] Push main menu Run|New Watch... RESULT: The New Watch dialog is opened within 1000ms 35 Javadoc Index Search open [ automated ] Push main menu View|Javadoc Index Search RESULT: Javadoc Index Search is opened within 1000ms. 36 Java Platform Manager open [ automated ] Push main menu Tools|Java Platform Manager RESULT: Java Platform Manager dialog is opened within 1000ms 37 Library Manager open [ automated ] Push main menu Tools|Library Manager RESULT: Library Manager dialog is opened within 1000ms 38 NetBeans Platform Manager open [ automated ] Push main menu Tools|NetBeans Platform Manager RESULT: NetBeans Platform Manager dialog is opened within 1000ms 39 Override and Implement Methods dialog open [ automated ] Open java file Push main menu Source|Override Methods... RESULT: Override and Implement Methods is opened within 1000ms 40 Go To Class dialog open [ automated ] Push main menu Edit|Go To Class... RESULT: The Go to Class dialog is opened within 1000ms 41 Go to Line dialog open [ automated ] Open java file Push main menu Edit|Go to Line... RESULT: The Go to Line dialog is opened within 1000ms 42 Auto Comment Tool open [ automated ] Open java file Push main menu Tools|Auto Comment... RESULT: Auto Comment Tool window is opened within 1000ms 43 Find in Source Editor dialog open [ automated ] Open java file Push CTRL+F RESULT: Find dialog is opened within 1000ms. 44 Internationalize dialog open [ automated ] Open java file Push main menu Tools|Internationalization|Internationalize... RESULT: Internationalize dialog is opened within 1000ms 45 Window_Documents dialog open [ automated ] Open 10 java files Push main menu Window|Window_Documents RESULT: Window_Documents window is opened within 1000ms 46 Add Server Instance dialog open [ automated ] Open Runtime view and select Server Registry | Tomcat 5 Servers node Push from popup menu Add Server... < RESULT: Add Server Instance dialog is opened within 1000ms.