TS 69 JavaFX Profiler

(Difference between revisions)
(Created page with '==Profiler Tests Specification== '''Author:''' [mailto:sunflower@netbeans.org Alexandr Scherbatiy] <br> '''Version:''' 1.3 <br> '''Last update:''' 04 August 2010 <br> '''Introduc…')
(Profiler Tests Specification)
 
Line 5: Line 5:
'''Introduction:'''  <br>
'''Introduction:'''  <br>
'''Comments:'''  <br>
'''Comments:'''  <br>
 +
 +
   
 +
   
 +
=== {{testcase|CPU mode}} ===
 +
*  Create a JavaFX Script project that contains a Stage.
 +
<pre> 
 +
import javafx.stage.*;
 +
 +
import javafx.scene.*;
 +
import javafx.scene.text.*;
 +
import javafx.scene.paint.*;
 +
import javafx.scene.effect.*;
 +
 +
 +
Stage {
 +
    title: "Hello World"
 +
    width: 250
 +
    height: 80
 +
    scene: Scene {
 +
        content: Text {
 +
            x: 10  y: 30
 +
            font: Font { size: 24 }
 +
            fill: Color.BLUE
 +
            effect: DropShadow{ offsetX: 3 offsetY: 3}
 +
            content: "Hello World!"
 +
        }
 +
    }
 +
}  </pre>
 +
       
 +
*  Press ''Profile Main Project...'' toolbar button. 
 +
*  Press ''OK'' on Enable Profiling dialog if it appears. 
 +
*  Select ''CPU''. 
 +
*  Press ''Run''. 
 +
* {{result|EXPECTED RESULT:  The application should start. }}
 +
*  Close the application. 
 +
* {{result|EXPECTED RESULT:  The application should stop. }}
 +
=== {{testcase|Live results}} ===
 +
*  Profile the Project from test case 5.1 (Do not close it). 
 +
*  Press ''Live Results'' button on the Profiler Control Panel in NetBeans. 
 +
*  Type ''run'' in the filter text field.
 +
*  Select ''javafxapplication.Main.javafx$run$(com.sun.javafx.runtime.sequence.Sequence)'' method and invoke ''Go to source''.
 +
* {{result|EXPECTED RESULT:  ''Main.fx'' file should open. }}
 +
=== {{testcase|Take Snapshot}}  ===
 +
*  Profile the Project from test case 5.1 (Do not close it). 
 +
*  Press ''Take Snapshot'' button on the Profiler Control Panel in NetBeans. 
 +
*  Select ''Main.main(String[])'' method and invoke ''Go to source''.
 +
*  Check ''Call Tree, Hot Spots, Compined'' and ''Info'' tabs.
 +
* {{result|EXPECTED RESULT:  ''Main.fx'' file should open. }}
 +
=== {{testcase|Memory mode}} ===
 +
*  Create a JavaFX Script project. 
 +
*  Press ''Profile Main Project...'' toolbar button. 
 +
*  Press ''OK'' on Enable Profiling dialog if it appears. 
 +
*  Select ''Memory''. 
 +
*  Press ''Run''. 
 +
* {{result|EXPECTED RESULT:  The application should start. }}
 +
*  Close the application. 
 +
* {{result|EXPECTED RESULT:  The application should stop. }}
 +
=== {{testcase|Monitor mode}} ===
 +
*  Create a JavaFX Script project. 
 +
*  Press ''Profile Main Project...'' toolbar button. 
 +
*  Press ''OK'' on Enable Profiling dialog if it appears. 
 +
*  Select ''Monitor''. 
 +
*  Press ''Run''. 
 +
* {{result|EXPECTED RESULT:  The application should start. }}
 +
*  Close the application. 
 +
* {{result|EXPECTED RESULT:  The application should stop. }}
 +
=== {{testcase|Threads}} ===
 +
*  Profile the Project in CPU mode. 
 +
*  Press ''Threads'' button on the Profiler Control Panel in NetBeans. 
 +
*  Press the icon to enable threads on the ''Threads'' window. 
 +
* {{result|EXPECTED RESULT:  Threads should be shown on the ''Threads'' window  }}
 +
=== {{testcase|VM Telemetry}} ===
 +
*  Profile the Project in CPU mode. 
 +
*  Press ''VM Telemetry'' button on the Profiler Control Panel in NetBeans. 
 +
* {{result|EXPECTED RESULT:  The ''VM Telemetry'' window should open. }}
 +
<br>

Current revision as of 14:07, 4 August 2010

Contents

Profiler Tests Specification

Author: Alexandr Scherbatiy
Version: 1.3
Last update: 04 August 2010
Introduction:
Comments:


CPU mode

  • Create a JavaFX Script project that contains a Stage.
   
import javafx.stage.*;

import javafx.scene.*;
import javafx.scene.text.*;
import javafx.scene.paint.*;
import javafx.scene.effect.*;


Stage {
    title: "Hello World"
    width: 250
    height: 80
    scene: Scene {
        content: Text {
            x: 10  y: 30
            font: Font { size: 24 }
            fill: Color.BLUE
            effect: DropShadow{ offsetX: 3 offsetY: 3}
            content: "Hello World!"
        }
    }
}   
  • Press Profile Main Project... toolbar button.
  • Press OK on Enable Profiling dialog if it appears.
  • Select CPU.
  • Press Run.
  • EXPECTED RESULT: The application should start.
  • Close the application.
  • EXPECTED RESULT: The application should stop.

Live results

  • Profile the Project from test case 5.1 (Do not close it).
  • Press Live Results button on the Profiler Control Panel in NetBeans.
  • Type run in the filter text field.
  • Select javafxapplication.Main.javafx$run$(com.sun.javafx.runtime.sequence.Sequence) method and invoke Go to source.
  • EXPECTED RESULT: Main.fx file should open.

Take Snapshot

  • Profile the Project from test case 5.1 (Do not close it).
  • Press Take Snapshot button on the Profiler Control Panel in NetBeans.
  • Select Main.main(String[]) method and invoke Go to source.
  • Check Call Tree, Hot Spots, Compined and Info tabs.
  • EXPECTED RESULT: Main.fx file should open.

Memory mode

  • Create a JavaFX Script project.
  • Press Profile Main Project... toolbar button.
  • Press OK on Enable Profiling dialog if it appears.
  • Select Memory.
  • Press Run.
  • EXPECTED RESULT: The application should start.
  • Close the application.
  • EXPECTED RESULT: The application should stop.

Monitor mode

  • Create a JavaFX Script project.
  • Press Profile Main Project... toolbar button.
  • Press OK on Enable Profiling dialog if it appears.
  • Select Monitor.
  • Press Run.
  • EXPECTED RESULT: The application should start.
  • Close the application.
  • EXPECTED RESULT: The application should stop.

Threads

  • Profile the Project in CPU mode.
  • Press Threads button on the Profiler Control Panel in NetBeans.
  • Press the icon to enable threads on the Threads window.
  • EXPECTED RESULT: Threads should be shown on the Threads window

VM Telemetry

  • Profile the Project in CPU mode.
  • Press VM Telemetry button on the Profiler Control Panel in NetBeans.
  • EXPECTED RESULT: The VM Telemetry window should open.


Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo